Scrum: a flexible project development

Conception of Scrum

Scrum is one of the first methodologies of cyclic functionality development and correction of the project on the basis of the analysis of feedback from users. The foundation is iterative development. It defines rules on which the list of requirements to a product should be planned and managed for achievement of the maximum profitability from the functionality. In general, each iteration can be described like that: planning - fixing - implementing - analyzing.

Scrum is a simple framework which can be used for the organization of the project team and achievement of the outcome with more productivity and with higher quality at the expense of the analysis of the completed works and correction of development direction between iterations. The methodology allows the project team to choose tasks which should be executed at first considering business priorities and technical possibilities, and also to determine how to implement them effectively. It allows to create conditions at which the team works with pleasure and with as much as possible productivity. For example, possibility of an independent choice of a volume and a way of the problem decision without external pressure allows all participants of the team to feel themselves as active players involved in the process, instead of simple executors from whom only accurate implementation of tasks is required.

Scrum focuses on constant definition of tasks priority being based on business goals. This approach increases utility and profitability of the project at its early stages. As at the stage of the initialization the project efficiency is almost impossible, The conception suggests to concentrate the project resources on the quality of development, and by the end of each iteration to have an intermediate product that can be implemented. For example, the outcome of iteration can be framework of web-site which is possible to be shown to the customer on presentation. Scrum methodology is oriented towards the operative adaptation of project team to changes in customer's requirements to a product. Such adaptation is reached at the expense of reception of a feedback by results of iteration. After iteration is finished the product is ready to be discussed and represented to the customer and users. Such an approach allows to collect the information easily, make corrections and change priorities of requirements. For example, if a site framework is to be shown to the potential users, then there will be many questions and feedbacks from users. On this basis Scrum team can correct the code which is written but not implemented yet.

Scrum motto says: analyze and adapt. You need to analyze what has been received and adapt it to a real situation, and then analyze again. As less formalism involved in the project as more flexible and efficient the project team can work. This is fundamental principle of Scrum methodology. But it does not mean that there will be absolutely no spaces for formal processes in the project. They should be enough for organization of effective interaction and management of the project. The formal part of Scrum consists of the following:

• roles: Master, Product Owner, Team.
• practices: Sprint, Scrum Meeting
• basic documents: Burn down Chart, Product Backlog, Sprint Backlog.

VIP Task Manager allows to apply the agile methodology to a project. The application has a set of tools that can be implemented to the successful accomplishment of Scrum project. In VIP Task Manager you can create Scum roles, manage Sprints, organize meetings and build charts.

Adding roles

In Resource View of VIP Task Manager you create resources and assign roles for each on them. For example, you need to add role "Scrum Master" and assign it to the project manager. Then you can set permissions for the role. As Scrum Master manages Scrum team and build plans he needs to have full access to the project task groups and tasks. So in Permission panel set all value "Allow".

Managing Sprint and organizing Meeting

In VIP Task Manager each Sprint can be represented as a task group with tasks inside. For example, bugs fixing is supposed to be finished in one Sprint. The Scrum Master creates task group "Mics. bug fixing" and fill it with a number of tasks. After the tasks were created Scrum Master assigns them to Scrum Team and VIP Task Manager automatically sends notifications to team. During execution of the task list Scrum Master can watch the progress in VIP Task Manager or just get notifications by email.

Scrum Master is a responsible person for organization of Meetings, and Team assists him. They can use VIP Task Manager to share tasks and plan Meeting well. Scrum Master generates meeting agenda in view of a task list and assigns tasks to Team members.