Agile scrum methodology is iterative and incremental software project management methodology. It is a process skeleton that contains set of practices and predefined roles.
Agile scrum delivers the product in iterative cycles called sprint. At the start of sprint iteration the team reviews what it must do. It then selects what it believes it can turn into an increment of shippable product. Sprint is time boxed and the team is committed to deliver it. Typically sprint is between 2-4 weeks.
Scrum process is shown in above image. The lower circle represents Sprint cycle, it represents an iteration of development activities that occur one after another. The output of each iteration is an increment version of the product. The upper circle represents the daily inspection occurs during the sprint iteration, in which individual team members meet to inspect each other’s activities and make appropriate adaptations.
Scrum has clearly defined roles.
Product owner is responsible for maintaining Product backlog and prioritising deliverables representing the interests of the stakeholders.
Scrum Master responsible for making everyone aware of the scrum process and ensuring it is properly being used.
Cross functional group of people responsible for delivering the product. In Scrum methodolgy people work as team and self organisation is the key practice.
Scrum process requires communication and working as team. It is achieved with the below meetings.
This occurs very 24 hrs. During this meeting each team member would talk about what they have done from last daily scrum? What is the plan for today? Any problems in accomplishing the task? This is timeboxed for maximum of 15 minutes.
Sprint Planning Meeting
During this meeting the team would select what work has to be done and prepare sprint backlog. This is timeboxed for maximum of 8 hrs.
Sprint Review Meeting
During this meeting the team and stakeholder would review what work has been done/not done. Present it to stakeholders.
During this meeting the team would discuss about what went well and what did not go well in the last sprint. Make continuous process improvements.
Scrum produces below artifacts for the project management.
Sprint burn down chart
Sprint burn down chart is a Daily progress for a Sprint over the sprint’s length. Burn down chart is a graphical representation of work left to do versus time. The outstanding work (or backlog) is often on the vertical axis, with time along the horizontal. That is, it is a run chart of outstanding work. It is useful for predicting when all of the work will be completed.
A prioritized list of high level requirements. It lists items adding value for the customer. It utilizes the simplest and the most effective way for prioritizing requests. The higher the items are located on the product backlog, the more detailed they are. Product backlog does not typically include the detailed requirement information.
A prioritized list of tasks to be completed during the sprint. The sprint backlog is the list of tasks that the Scrum team is committing that they will complete in the current sprint. Items on the sprint backlog are drawn from the Product Backlog, by the team based on the priorities set by the Product Owner and the team's perception of the time it will take to complete the various features. The sprint backlog is very commonly maintained as an Excel spreadsheet but it is also possible to use your defect tracking system or any of a number of software products designed specifically for Scrum or agile.
Three legs of scrum implementation Process
It means that those aspects of the process that affect the outcome must be visible to those controlling the process.
The various aspects of the process must be inspected frequently enough that unacceptable variances can be detected easily.
If the inspection determines one or more aspects of the process are outside acceptable limits, the inspector must adjust the process. The adjustment should be as quickly as possible, so that the further deviation is reduced.