What is Scrum/Iteration Management
Scrum is an agile process framework that has proven to work in project/product development environments that experience rapid change and/or emergent requirements. The complexity in these efforts can result from the domain, number of people involved, compression in time, emergent feedback and more. Scrum is suited for projects that require the combined intellect of more than one individual. The complex problems that are appropriate to tackle with Scrum require the combined focus of a team.Scrum is a project or product development method that contains short rapid cycles for evolving product. These rapid cycles have enabled software development to move from an area of almost pure art, to creative craft, with well understood engineering practices that support the craft.Scrum has the power to transform project management across every industry, every business, and even across life in general. By using Scrum, you’ll become more Agile, discovering how to react more quickly and respond more accurately to the inevitable change that comes your way. And by staying focused, collaborating, and communicating, you can accomplish what truly needs to be done successfully.
1.The reason for a well-run agile scrum project being more effective is that it balances the three main conflicts of managing software projects
Team
The development team needs a fixed scope of work at maximum efficiency.
Business
The business needs to change the scope as it learns more information and reacts to project needs and market forces.
Delivery
Delivery pressures force companies to quickly release insecure and poor quality product.
2. The strategies used to address these competing pressures
Viable product
Release a minimally viable product, that's aligned to the key benefits ASAP. This allows the business to start getting the key benefits as soon as possible.
Changing scope
Allow the business to change the scope regularly, at agreed intervals. Producing a solution that is closer aligned to the needs of the business, and accounts for new learnings and improved understanding of capability.
Tolerant solution
Automate the testing and provisioning of the solution. Allowing the solution to be tolerant to changes in scope and functionality.
3. The tactics we use to deliver these strategies
The sprint
The sprint is the key contract of engagement between the development team and the business. It’s an agreed period within which no changes are made, with the agreement that at the end of the period, all changes can be made.
Automated testing
We shift resourcing out of analysis and into testing. No software is released without bugs, and the longer we spend refining and testing software the better it becomes. Hence we assign more resources to testing and sometimes write the tests before the software.
The story
The backlog of stories is the list of what the business wants. A story is written in business language, not technical language. It has an emphasis on identifying how things will look, behave, and how the business will accept it as complete and delivered
The key activities that we use.
1. The showcase
A regular demo of progress and constructive feedback
Occurance
Occurs at the end of each sprint (every 2 weeks).
Requirement
A sprint worth of work, all stories to be up to date.
Purpose
1. Demonstrate to the business what has been achieved in the previous sprint.
2. Official forum for the business to accept stories as completed.
3. Provide feedback and detailed clarification.
4. Provide learnings and up to date information to carry into the story prioritisation task.
2. The sprint kick off
Prioritise the next set of work packs.
Occurance
Occurs at the beginning of each sprint (every two weeks).
Requirement
A set of stories clearly prioritised by the business.
Purpose
Establish the work programme for the next two weeks.
Roles and Responsibilities
- Product Owner- Be on hand for any questions that the team have regarding deliverables, and any ramifications to priorities based on discovered interdependencies and blockers
- Scrum Master- Runs the meeting. Keeps track of the story (effort) points assigned during the process and ensures the team is not overbooked.
- Developers- Present achievements and demonstrate deliverables.
Key activities
- 1. Review every story and break down into assignable tasks.
- 2. Review interdependencies.
- 3. Re-prioritise story list based on detailed planning information.
3. The stand-up
Daily check-in with delivery team on progress / blockers.
Occurance
Occurs every morning.
Requirement
All team members.
Purpose
1. Informs team members of any potential delays.
2. Allows team members to cross pollinate expertise to help one another.
3. Informs Scrum Master of potential blockages.
Roles and Responsibilities
- All- Update the team on tasks completed, planned tasks for the day, and any blockers.
Key activities
- Each team member update the rest of the team on what they achieved the day before, and what they plan to achieve for today.
4. Sprint retrospective
Review and lessons learned.
Occurance
Happens after the showcase for each sprint.
Requirement
A set of stories clearly prioritised by the business.
Purpose
Continuous improvement.
Roles and Responsibilities
- Whoever and whatever is appropriate.
Key activities
- 1. Review the previous sprint.
- 2. Identify what went well and what didn't.
- 3. Identify ways to improve the project performance.