2. Why Agile Maturity
Assessment?
Vision: help teams and companies ensure continuous
measurement and improvement of their agility and quality.
Provides a clear insight on current state of the team
Analyze the sprint execution
Identify pain areas
Suggest Improvements
Help increase overall productivity
3. What is Agile Maturity
Assessment?
Experienced Agile Expert reviews every agile team once every
sprint
Assess the team on their current practices
Come up with team ratings ( Expert , Medium and Beginner)
4. How we do Agile Maturity
Assessment?
Product
Owner
Development
Team
Scrum
Master
Product
Backlog
Lorem ipsum dolor sit amet, consectetur adipiscing elit.
Phasellus nibh dui, rutrumnoninterdum sed, porttitor non
augue. Morbi adipiscing vulputatediam nec blandit.
Aenean sed viverra magna. Pellentesqueac quam velit.
Cras pharetra, urna nec mattis interdum, tortor orci iaculis
tellus, nec lobortis sapien justoquis felis. In hac habitasse
platea dictumst. Phasellusposuere cursus lacus, non
conguemassa fringilla eu. Sed viverra vulputate quam, in
aliquam nulla tinciduntat. Sed posuereest at nisl cursus
mollis. Aliquam erat volutpat. Curabitur pretiumturpis vel
nibh adipiscing sed molestieeros euismod. Pellentesque
pretium sagittis ipsum, vitaecondimentum risushendrerit
eu. Cras ullamcorper massa in eros lobortis sodales.
Integer ultrices molestieturpis nec cursus. Etiam tempor
vestibulum mollis. Sed dictum condimentum nibh, eget
tincidunt libero sodales ac. Aliquam sed justo nisl, eu mollis
justo. Curabitur egestas libero nec quam fringilla
bibendum. Ut hendrerit quam et nibh volutpat vitae
pretium erat scelerisque. Phasellus id est est.
Increment
Sprint
Backlog
Lorem ipsum dolor sit amet, consectetur adipiscing elit.
Phasellus nibh dui, rutrumnoninterdum sed, porttitor non
augue. Morbi adipiscing vulputatediam nec blandit.
Aenean sed viverra magna. Pellentesqueac quam velit.
Cras pharetra, urna nec mattis interdum, tortor orci iaculis
tellus, nec lobortis sapien justoquis felis. In hac habitasse
platea dictumst. Phasellusposuere cursus lacus, non congue
massa fringilla eu. Sed viverra vulputate quam, in aliquam
nulla tincidunt at. Sed posuereest at nisl cursus mollis.
Aliquam erat volutpat. Curabitur pretiumturpis vel nibh
adipiscing sed molestieeros euismod. Pellentesquepretium
sagittis ipsum, vitaecondimentumrisus hendrerit eu. Cras
ullamcorper massa in eros lobortis sodales. Integer ultrices
molestieturpis nec cursus. Etiam tempor vestibulummollis.
Sed dictum condimentum nibh, eget tinciduntlibero sodales
ac. Aliquam sed justo nisl, eu mollis justo. Curabitur egestas
libero nec quam fringilla bibendum. Ut hendrerit quam et
nibh volutpat vitaepretium erat scelerisque. Phasellus id
est est.
Sprint
Planning
Meeting
Retrospective Sprint
Review
Daily Scrum
Sprint
o Well Maintained
Product Backlog
o Is Team
positioned to
deliver value
o How would team
deliver sprint goal
o Extreme
programming
practices
o Inspect and
Adapt
5. So What is Value Add?
Well maintained backlog (Product Backlog)
Are all stories prioritized
Is team aware of PO’s vision
Is there a release plan
All stories comply with DOR (Definition Of Ready)
6. So What is Value Add?
Is team positioned to deliver value (Sprint planning)
Does team understand all the stories and their purpose
Are the stories small enough to be delivered with in sprint
Are stories testable/demo-able
How are stories estimated
Are stories refined
7. So What is Value Add?
How would team deliver sprint goal (Sprint backlog)
Are all stories split into tasks
Is every team member is involved in splitting the tasks
Is burndown available
Is Definition of Done defined and adhered to
Are task assigned upfront
8. So What is Value Add?
Extreme programming practices (Sprint)
Are code reviews done and are effective
Is code being continuously integrated
Is code analysis done
Unit Testing done
Functional Testing done
Does team pay heed to failing build
Are sprint demos done
Code refactoring (Simple and incremental design)
9. So What is Value Add?
Inspect and Adapt (Retrospective)
Does team inspect the good, bad and possible
improvements in the sprint
Does team adapts to the inspection in successive sprints