Your SlideShare is downloading. ×
Pmi   agile planning, inspection and adaption
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

Pmi agile planning, inspection and adaption

120

Published on

0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
120
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
7
Comments
0
Likes
0
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
  • http://toolsforagile.com/blog/wp-content/uploads/2008/07/word_cloud.pngSince Scrum has the highest adoption rate among agile practices, we’ll be focusing on this framework(not XP, Kanban, etc.)
  • Quality: also focused on what the customer expected
  • Have to mention dedicated teams doing the work
  • Image: http://www.etftrends.com/wp-content/uploads/2011/03/ETF-Spotlight1.jpg
  • Image: http://lh6.ggpht.com/sritsqldotnet/SGBLTDURKtI/AAAAAAAAADw/CGJ5OhfS3VE/Five%20Levels%20of%20Planning%5B2%5D.png
  • http://farm1.static.flickr.com/198/466161899_339852d2a3_o.pngYou‘llhave a more realisticroadmapusingthisapproach ...
  • Dean Leffingwell: Scaling Software Agility
  • http://www.archives.gov/records-mgmt/toolkit/fbi/rma_transition/image5_3.gifBacklog contains the requirements– same as WBS -- we just don’t plan them out until we are sure we are going to deliver themAssume: 6 month project
  • http://scalingsoftwareagility.files.wordpress.com/2008/03/draft-release-plan.jpgRelease plan is a little closer to what a WBS is, but still less planning than is necessary for this far outCone of uncertaintyIntegrated and tested at EVERY iteration boundary
  • http://sandersconsulting.com/wp-content/uploads/2011/06/bigvssmall.jpgSprint plan is a WBS, just on a smaller scale we are sure we can deliver
  • http://www.pensionriskmatters.com/uploads/image/Risk%20Cubes.jpgWhich reduces riskPotentiallyshippable product every sprint
  • Use estimates, relative sizing, velocityFocus on velocity, allowing a team to understand what they can accomplish in a certain timeBreak after activity
  • Problem:Only answers the questions: Are we on time? Are we on budget? (based on the original plan)Doesn’t answer: Are we delivering the right thing, right now?Not changing our approach, asking people to work longer == less qualityDoesn’t account for unknown integration, testing work (defects, etc.)
  • Is it truly controllable?Invite change from the business, a collaboration not a contract
  • Better velocity charts here!
  • http://scalingsoftwareagility.files.wordpress.com/2008/03/draft-release-plan.jpg
  • Split this into multiple slidesOn-Budget: Fixed cost of teamAdd an iteration, more costRemove an iteration, less cost
  • Things that are marked as done are ACTUALLY Done, Done!not in progress on a featureNot waiting on QA/testingNot waiting on integration, etc.Cite quote
  • Don’t allow your tech debt to growQuality metrics: Look at the system and how it’s incentivized (to find defects, or to add value?)Check-In on deep dives into any topics!Break!
  • http://cfconference.files.wordpress.com/2011/05/thank-you-rocks.jpg
  • Transcript

    • 1. Agile Planning, Inspection & Adaption
    • 2.  8+ yrs as Software Developer 6+ yrs as Scrum Master and Coach 1 year as Product Owner Internal Coach @ Rally Software Servant leader to the agile community Passionate about agile teams, metrics and using agile/lean concepts in everyday life Contact Info:  tsheridan@rallydev.com
    • 3.  10+ years in Software & Hardware Industries Certified Project Management Professional Certified Scrum Master and Professional External Agile Coach (to many) Internal Agile Coach at RightNow Technologies Agile Community Contributor and Teacher Contact Info:  erin@skipstoneconsulting.com  @coachatplay
    • 4.  Name Company Position Experience with Agile
    • 5.  Introductions Approaches and Value Agile Planning Inspecting Adapting Q&A
    • 6. What do you want to learn? What seems the hard or impossible?http://josvoskuil.files.wordpress.com/2009/02/think.png
    • 7. EVM and Agile, how each determines value
    • 8. • Agile approach EVM approach – Value: Decided and  Value = Amount prioritized by the PO/Customer/Business, Budgeted. Guided by guided by Vision project plan – Asks 3 Questions • Delivering highest value  Asks 2 Questions features? ▪ On Schedule? • On Schedule? • Delivering Quality? ▪ On Budget? – Focused on planning  Focus on “The Plan” – Rearrange how we work (vertical slices)
    • 9. Triple Constraints Fixed Requirements Resources Time Value Driven Plan DrivenEstimated Resources Time Features
    • 10. Daily Standup 2 Week Iteration Iteration Planning Demo, Review & Meeting RetrospectiveProduct Tasks Potentially ShippableBacklog Product Increment
    • 11.  PO acting as proxy of the customer / stakeholders Fast feedback by delivering working software Prioritizing a backlog of features / requirements Guided by product vision Value vs. Risk decisions
    • 12. Translating into the agile world
    • 13.  For military folks: “Commanders Intent”  To make people understand why they are doing stuff
    • 14.  High level themes/initiatives (“broad strokes”) Annual or Quarterly
    • 15.  NOT architectural layers Story 1 Story 2 Deliver value quickly Use this feedback to GUI deliver more value Business Logic Database
    • 16. Ball Point Game
    • 17. Metrics and what the data is telling us
    • 18.  EVM Approach
    • 19.  Agile Metric: velocity  Stabilize, then use for forecasting
    • 20.  Burndowns Burnups
    • 21.  Real  Good decisions based on real data  Constantly updated  No surprises! (no “let’s see what happens?”) Fake  Bad decisions  “The optimism of hope above experience”
    • 22.  Shippable product EVERY iteration Designed, Developed and Tested Fast Feedback! Not leaving stuff until the end Metric: # of defects escaping the iteration Metric: Code/Unit test coverage? Measurement = working software delivered (value!)
    • 23. Retros to help your teams become more effective
    • 24. Discuss and ConfirmGather Data Refine Action Items
    • 25.  Silent Brainstorming (w/ post its) Time boxed (15-30min) 3-4 categories  Start, Stop, Continue, Shouts  Strong, Weak, Improving http://www.selfishprogramming.com/2009/12/08/agile-winter-school
    • 26.  Time boxed Walk through each comment in the Data Gathering exercise Find common themes and categories Brainstorm actionableitems for each categories http://fabiopereira.me/blog/tag/thoughtworks/
    • 27.  Time boxed Voting Give everyone 5-10 dot stickers Ask them to spend their dots on their favorite actionable items http://www.innovationtools.com/Articles/ArticleDetails.asp?a=141
    • 28.  Plus/delta Start/Stop/Continue 4 Quadrants Timeline Many more
    • 29.  Running them Locally:  Whiteboard and Post-Its Remote Folks  corkboard.me  googledocs  Whatever allows the voice of remote folks to be heard
    • 30. Review parking lot backlog
    • 31. This Workshop

    ×