Your SlideShare is downloading. ×
Agile in short projects
Agile in short projects
Agile in short projects
Agile in short projects
Agile in short projects
Agile in short projects
Agile in short projects
Agile in short projects
Agile in short projects
Agile in short projects
Agile in short projects
Agile in short projects
Agile in short projects
Agile in short projects
Agile in short projects
Agile in short projects
Agile in short projects
Agile in short projects
Agile in short projects
Agile in short projects
Agile in short projects
Agile in short projects
Agile in short projects
Agile in short projects
Agile in short projects
Agile in short projects
Agile in short projects
Agile in short projects
Agile in short projects
Agile in short projects
Agile in short projects
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×
Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

Agile in short projects

760

Published on

Published in: Technology
0 Comments
2 Likes
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total Views
760
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
50
Comments
0
Likes
2
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide

Transcript

  • 1. Agile in Short Projects:A One Team Experience 0
  • 2. How do we define short projects? 1 week to 2 months 1 or 2 person teams 1
  • 3. What’s it like in the short duration, smallprojects world today? 2
  • 4. Agenda Background 2010 “A Pivotal Year” Our macro group backlog Inspecting and Adapting Key takeaways 3
  • 5. When webegan… 4
  • 6. What the team looked like before… RAD Global Coordinators US Coordinators Europe Coordinators Onsite Technical Onsite Technical PM (Europe) PM (India) Developer Developer Developer Developer Developer Developer Developer Developer Developer Developer Developer Developer Developer Developer Developer Developer 5
  • 7. Challenges Developers lacked understanding of big picture Requirements would be lost by the time they reached developers Quality issues Support done by developers Changes in requirements, priorities & timelines Lack of a uniform way to communicate with stakeholders No cross sharing of knowledge within teams in different locations 6
  • 8. Agenda Background 2010 “A Pivotal Year” Our macro group backlog Inspecting and Adapting Key takeaways 7
  • 9. Reorganizing the team 8
  • 10. Brain-storming a vision 9
  • 11. Our longer term vision We deliver best in class service and high quality solutions to our end users The project experience will feel as ‘one team’ We provide a Our quality consistent experience improves and when delivering sponsors our projects are delighted! Adapt relevant We build an agile practices that exceptional pool of improve upon service talent to draw upon delivery model 10
  • 12. Let’s use agroup backlog! 11
  • 13. Agenda Background 2010 “A Pivotal Year” Our macro group backlog Inspecting and Adapting Key takeaways 12
  • 14. A “macro” group backlog As a user, I want to adopt relevant agile As a user, practices that make As a user, I As a user, I want to communicated with I want to define sense to improve upon want to how projects are define team our end users our service delivery prioritized model roles consistently As a user, I want to define criteria for SIA development As a user, I want to define a support process As a user, I want to setup a process to gather stakeholders feedback on projects 13
  • 15. The fruits of ourbacklog approach 14
  • 16. What do team roles look like today? SM/portfolio PO Architect Dev PO Architect Dev Extended pool 15
  • 17. PO – Developer pairing: requirements 16
  • 18. Our projects are morefocused… what do we take on? 17
  • 19. Support is a separate entity The development teams are now dedicated and can finish their commitments on time!!! 18
  • 20. hen … w ag e cy ss en me st r si u on g o c n re eri o vM li de 19
  • 21. Mini release plan Story Headline Sprint 1 GUI for filtering the reports Tables with the same structures as current Access prototype (Nov 1) Data loads from existing Access db to local MS SQL tables SQL server environment setup Sprint 2 SQL stored procedures to return data for 6 reports Logic for query to retrieve the data for 6 reports (Nov 8) UI ready for multiple reports in Excel (6 reports) Aggregation level logic for reports (6 reports) Script with all table structures (initial data load) Performance testing of complex queries Sprint 3 SQL stored procedures to return data for 5 reports Logic for query to retrieve the data for 5 reports (Nov 15) UI ready for multiple reports in Excel (5 reports) Aggregation level logic for reports (5 reports) Scripts to load the Gross members data Data load from Access to the Medical and Demographic Lookup tables Performance testing of complex queries Sprint 4 End to end integration testing Mechanism for client to update state scenarios post initial load (Nov 21) Documentation for front end Documentation for data model and data load scripts 20
  • 22. Mini product backlog 21
  • 23. Retro output 22
  • 24. Agenda Background 2010 “A Pivotal Year” Our macro group backlog Inspecting and Adapting Key takeaways 23
  • 25. What is working? More transparency, cross sharing and Clear roles empowered Direct contact with teams… stakeholders More consistency working with end users Group & project sprint reviews PO “Scrum of scrums” Regular pipeline discussions Group & project retrospectives 24
  • 26. What can we improve? Bring more consistency across all projects Continue to focus on quality Continue to bring transparency Bring innovation to the way we work 25
  • 27. Agenda Background 2010 “A Pivotal Year” Our macro group backlog Inspecting and Adapting Key takeaways 26
  • 28. In summary Today… Before… Flat structure Hierarchical structure Entire team is empowered PMs empowered Developers understand & Developers lacked contribute to vision understanding of BIG picture Higher quality apps Many quality issues Support separate entity Dev teams not dedicated to ‘just’ development Projects are time-boxed Changes in priorities, timelines More uniform experience with & requirements clients The experience from the client More cross sharing of changed depending who they knowledge work with Lack of a uniform way to communicate with stakeholders No cross sharing of knowledge within teams 27
  • 29. Key takeaways… Our macro backlog is a way to ensure we make baby steps towards our grand vision Focus on starting small and try ideas out with a few projects (hence why the stories in our macro backlog are helpful) Experiment, be patient, be open to change and expect things won’t work and you have to move on to the next thing Ensure the team believes! 28
  • 30. Q&A Yvannova_Montalvo@mckinsey.com Jyoti_Prakash_Datta@mckinsey.com 29
  • 31. References prince2-small-projects.jpg. Sep 23, 2007. Prince 2 Training Website. Web. 16 Jan 2012. Retrieved from http://www.prince2training-uk.org/using-prince2-in-small-projects istock_puzzle-businessman.jpg. Apr 1, 2008. Sherman Capital Advisors. Web. 16 Jan 2012. Retrieved from url http://shermancapitaladvisors.com Vision.jpg. The Attraction Institute. Web. 16 Jan 2012. Retrieved from url http://attractioninstitute.org lightbulb-idea-124411-05112010-124411-05112010.jpg. Business Opportunities Weblog Network. Web. 16 Jan 2012. Retrieved from url http://www.business- opportunities.biz/2010/05/11/is-my-business-idea-a-good-one/ Focus_Group.jpg. Web. 16 Jan 2012. Retrieved from url http://getpaidcentral.com CLIPART_OF_15195_SM_2.jpg. Adoptive Families Associations of BC. Web. 16 Jan 2012. Retrieved from url http:// adoptionsupportinterior.blogspot.com 30

×