Scrum provides a foundation for agile practices like self-organization, transparency, and collaboration. However, Scrum alone may not address challenges like leadership, risk management, governance, and client engagement. The document proposes extending Scrum with additional practices from frameworks like Disciplined Agile Delivery to provide specialist roles, technical practices, goal-driven governance, and improved stakeholder engagement for complex projects.
Berhampur 70918*19311 CALL GIRLS IN ESCORT SERVICE WE ARE PROVIDING
We are using scrum, but now what?
1. ”We are using Scrum, but now what?”
Julian Holmes, Founder of AgileMentors
2. Agenda
▪ Scrum as a Foundation
▪ Building on Scrum
▪ Challenges that require additional practices
–
–
–
–
Self-organisation v Leadership
Risk Management
Commercial Governance
Client engagement
▪ Questions
3. Scrum as a Foundation
▪ Very simple
▪ Team decides on level of
ceremony
▪ Regular feedback
▪ Queuing theory, reduced
handoffs
▪ Transparency
▪ Focus effort and prioritisation
▪ Ownership
▪ Potentially 'shippable'
products
4. Scrum is still the “King” of Agile methods
▪ But the largest benefits come from a
a hybrid approach
▪ E.g. XP helps fill the technical gap
purposely left by Scrum
1
DSDM Atern
1
1
Agile UP
2
2
Lean
2
2
XP
4
54
85%
4
Kanban
7
9
11
Custom Hybrid
Scrum
7th Annual State of Agile Development Survey - VersionOne, February 2013
5. DAD as a Scrum Hybrid
“The Disciplined Agile Delivery
decision process framework is a
people-first, learning-oriented
hybrid agile approach to IT
solution delivery. It has a riskvalue delivery lifecycle, is goaldriven, is enterprise aware, and is
scalable.”
6. DAD Roles
▪ Recognition that other roles
need to exist
▪ Architecture will be a focus for
complex solutions
▪ Not all the skills and
responsibilities of an
organisation can be in the team
7. Agile Team Leader
▪ Can we expect all Agile teams to be
completely self-organising?
▪ Some “leadership” may be required
▪ An extension to the Scrum Master role
▪ Not management, true leadership
▪ A “servant leader”
14. Stakeholder Engagement
▪ Ideally through the Product Owner
▪ Availability or consensus may be an
issue:
– Inception Deck workshop
– Product Owner Proxy
– Backlog “Grooming” workshops