Scrum can be a solid foundation for software development teams. In the 24 years since
Eight Steps to Improvement
Step 2: Use flow theory to create a focus on finishing and to avoid handoffs,
Step 3: Base this new Scrum on Lean. Include systems-thinking to help you see the big picture and have explicit workflow to facilitate collaboration.
Step 4: Test-first to some extent relating both to requirements and development understanding and requirements to implementation. Ask the questions:
- When given a requirement: how will I know I’ve done this? See How to Start with ATDD using BDD
- When about to implement it: how will I test this? See Define Tests up Front.
Step 5: use Minimum Business Increments. While MVPs are in vogue, most companies are not making an investment to see if a new product is useful but
Step 6: include management in improving the process. Servant leadership is to the organization not to the team. See Toward Middle-Up-Down Management:
Step 7: Have everyone agree to the guardrails. The basic agreements are:
- Work on items that will realize the greatest amount of business value across the enterprise.
- Collaborate with each other
in orderto maximize the realization of business value across the enterprise.
- Ensure that
all work will be madevisible.
- Take the necessary steps to sustain or increase predictability.
- Keep the work throughout the value stream within capacity.
- Encourage everyone to strive for continuous improvement.
Step 8: Continuously improve by deepening your understanding of software development by using PDSA in your retros to improve your understanding of the challenges being faced