Agile lessons learned in the Microsoft ALM Rangers
•Download as PPTX, PDF•
1 like•885 views
The document discusses lessons learned from the Microsoft ALM Rangers team regarding agile practices. It provides an overview of scrum basics including that the product owner owns the backlog, the team completes work in sprints, and sprints end with a review and retrospective. It also notes some key lessons learned such as the importance of passion, priority definitions, light ceremonies, time as an engineering constraint, communication over metrics, and video not being a nice-to-have.
Recommended
More Related Content
What's hot
What's hot (20)
Viewers also liked
Viewers also liked (10)
Similar to Agile lessons learned in the Microsoft ALM Rangers
Similar to Agile lessons learned in the Microsoft ALM Rangers (20)
More from Robert MacLean
More from Robert MacLean (20)
Recently uploaded
Recently uploaded (20)
Agile lessons learned in the Microsoft ALM Rangers
- 1. Agile lessons learned in the Microsoft ALM Rangers team
- 2. Hi, I’m Robert Microsoft AppFactory Senior Developer Microsoft ALM Ranger @rmaclean ♥ www.sadev.co.za
- 4. Learn more about the Rangers at aka.ms/vsarunderstand
- 8. See more at aka.ms/vsarsolutions
- 9. Constant improvement Shared at vsarguidance.codeplex.com
- 10. Scrum basics Product owner owns product backlog Team completes work in sprints Daily meeting for 15min to assess progress Scrum master keeps team focused & removes blockers Each sprint delivers potentially shippable product Each sprint ends with a review & retrospective
- 11. Ruck compare Product owner owns product backlog Team completes work in sprints Weekly meeting for 15+15min to assess progress + video recorded Ruck master keeps team focused & removes blockers Each sprint delivers potentially shippable product Each sprint ends with a review, retrospective & video
- 13. An Amazing Team
- 16. Key things we’ve learnt Passion wins Definition of Priority Ceremony needs to be light Time as an engineering constraint Communication is more important than metrics Video isn’t a nice to have Go to: aka.ms/vsarunderstand
Editor's Notes
- Microsoft Visual Studio Application Lifecycle Management Rangers
- Goal: How we leverage Scrum with non-dedicated and non-collocated teams Useful for those who have community & open source stuff. Those investing in 10% time projects.
- Photo: https://www.flickr.com/photos/31157752@N04/5294682340/in/photostream/ Microsoft Visual Studio Application Lifecycle Management Rangers Started in March 2006 Came out of our consulting services division We see ourselves like a forest ranger
- Services & non-services; mvps; fanatics; PASSION NON-DEDICATED
- Different countries; cultures; languages; time-zones
- Family > Work > Rangers
- 47 solutions focused on a variety of ALM, Visual Studio & TFS gaps Numerous books & publications Upcoming is a book on our learnings with this Sampling Unit test generator Branching/Merging guidance Visual Studio quick reference guide FlightPlan
- Constant improvement Mention Brians Book
- Favour scrum – ease of onboading, tooling with scrum templates etc…
- Meeting – mention Lync
- Ceremony needs to be kept low Max time per project Keep the passion high Stakeholders to give them etas Roadmap Clear plan, communicated to the team during kick off
- Win/lose as one Ideal is 7 +/- 2 Upper limit at 10 Project Owner (owns the backlog, subject matter expert) Has a backup Limit to three inflight projects Project Lead (dev/tech) Program Manager (rangers representive; PM; tester; scrum master; development; review) Has a backup Limit to three inflight projects Creators Testers
- https://www.flickr.com/photos/ny156uk/2671781204/in/photolist-556ztb-79smns-a4w6B5-a1tXGg We use sprints as normal Longer time than normal as we have fewer hours available Each team delivers a sprint video TRP : Training/Research/Plan First sprint, can be a half sprint QP : Quality Process Final sprint QA – not an excuse for no quality Mention gated checkin, style cop, fxcop etc…
- Epics!!! We have a set time, include that in your engineering We use story points for sizing Max of 3 SP. Stable Velocity is not an issue – we have a goal velocity which is based off previous experience & if we go above it bonus. If we go below it, we review the reasons, adjust goal velocity with new info, adjust the backlog and move along. The other side is that passion is a powerful motivator for getting stuff done. On the projects I’ve seen, passion trumps velocity. Planning poker is used – mention TFS tools Can vote for ½, 1, 3, 5, 8