Development teams often get stuck when they encounter real-life challenges that are not addressed by most formal Agile/Scrum training, especially when they try to implement Agile/Scrum in a traditional/Waterfall environment.
- How do you handle a sponsor that wants regular “percentage complete” progress reporting and release schedules? Isn’t Agile/Scrum supposed to free us of this reporting?
- How can you deal with reliance on other groups/functions that still practice traditional or Waterfall project management?
- My organization wants us to use formal risk assessment – isn’t that against the spirit of Agile?
- My sponsor insists on the project fitting into a feasibility gating project framework. That doesn’t sound very Agile.
- How can I coordinate multiple teams to deliver in a synchronized, smooth way?
In this content area, we share the top challenges encountered by Scrum teams and our best, proven solutions to deal with them. Some examples and tips:
- Agile does not mean a scope free-for-all: create and manage a backlog instead. Try creating a “Minimum Valuable Product” and take things out of your backlog that don’t create value.
Requirements – What really works?
- Most teams only need: acceptance criteria, process/business flows, business rules and visuals – wireframes, mapping documents, value mapping. What do you think you need and why?
Release Planning and Beyond
- Develop a roadmap showing leadership the underlying assumptions and delivery plan of work. They’ll feel better and it will build trust.
Dependencies Outside of Your Team
- Identify and place them on your roadmap – examples include: architecture, database etc. Understanding the environment and the constraints within it are key.
- Create a visual and update every month – Scrum will point out issues and risks – what will you do with this rich data?