Get Ready For Your First Iteration
Upcoming SlideShare
Loading in...5
×
 

Like this? Share it with your network

Share

Get Ready For Your First Iteration

on

  • 2,820 views

How do you know you are ready to start iterating? In some cases, very little is needed before the first iteration. In other cases, rushing to iterate (because you were told to) can lead to weeks of ...

How do you know you are ready to start iterating? In some cases, very little is needed before the first iteration. In other cases, rushing to iterate (because you were told to) can lead to weeks of time wasted overly focused on delivering a poorly understood product.

This tutorial provides concrete tools for discovering your product context and assessing whether you are ready to start building and / or iterating. Participants will learn tools for defining how much process you need and tools for truly understanding what you are building and why, as well as who will use it, why they will (or will not) use it and why.

Statistics

Views

Total Views
2,820
Views on SlideShare
2,382
Embed Views
438

Actions

Likes
0
Downloads
75
Comments
0

4 Embeds 438

http://blogs.agilefaqs.com 428
http://www.slideshare.net 6
http://static.slidesharecdn.com 3
http://agilefaqs.com 1

Accessibility

Categories

Upload Details

Uploaded via as Adobe PDF

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

Get Ready For Your First Iteration Presentation Transcript

  • 1. Getting Ready To Produce What's Needed Before Iteration1
  • 2. Questions and Discussions are Welcome
  • 3. Who Are You? - introduce yourself as if you were your product -
  • 4. DevJam Jams
  • 5. DevJam Agility Creating Community and Common Vision Form Communities (Chartering) Compose a Product (Personas – Story Maps – Design) Create an Eco-System (Iteration 0 – Common Workspace) Prioritizing and Planning Product Releases (Releases - Priorities - Estimates) Iterative Delivery (Iterations – Stories/Tasks - Estimates) Iterative Delivery and Tuning Staying Connected (Daily Standup – Common Workspace) Tracking Progress (Task Wall - Burnchart - Velocity) Technical Agility (Continuous Integration – Test Driven) Delivering Value (Acceptance Test - Story Sign Off) Tuning and Improving Validating Progress (Review / Product Presentation) Reflect and Improve (Retrospective)
  • 6. Preproduction ( getting ready to produce ) ______________________ Creating Community and Common Vision Form Communities (Chartering) Composing a Product (Personas – Story Maps) Create an Eco-System (Iteration 0 – Common Workspace)
  • 7. Preproduction Tools 1) Why are you building? ( charter ) 2) Who is buying (in)? ( personas ) 3) What do they do? ( story maps ) 4) Which (to build) first? ( planning ) 5) When is there value? ( story tests )
  • 8. Chartering ( why are you building? )
  • 9. Chartering (a project story) Meet as a community to discuss: Elevator Pitch Goals - Success Measures Community Mapping Values - Working Agreements Strengths - Challenges Cadence
  • 10. Telling a Project Story ( charter )
  • 11. Elevator Pitch What are you building and why? ( keep it short and memorable )
  • 12. Measurable Goals Project Charter: <name removed > / Time Frame: start of Q3 and end of Q4 Elevator Pitch: Less papers means less manual mistakes; build a new system with a sustainable process Goals Prove proposed technology - Move away from paper process Usable system to pilot - Validate the ability to have dynamic business rules Adapt to business and regulatory environment - Show value of iterative development Build confidence and buy in with business users - Fine tuning estimates (validate sizing) Have fun and learn (new knowledge) Value to Company Build efficiencies in field using technology - Shorter processing time with fewer errors Straight through efficiencies - Increase service level agreements with customer Increase business feedback Success Measures There is continuous feedback from business community Plans are reviewed and updated based on iteration outcome Community is improving on delivering on commitments and learning from each delivery Status of request on-line are viewable Business rules can change to manage work load
  • 13. What Does Success Looks Like? - the blur is intentional -
  • 14. Create a short elevator pitch Include 2 goals w/ success measures _______________________________ Find someone to pair with and share your project story
  • 15. - did you fail? - - when is failure good? -
  • 16. Personas ( who is buying / buying in? )
  • 17. Personas Are More Than Actors Personas represent people & clarify product value
  • 18. Our Product - Point of Sale App Create a Point of Sale application 10 local stores Application runs only on registers Registers are new, running Tomcat & MySQL Another system provides item price & description
  • 19. Pragmatic POS Personas
  • 20. Emergent Personas
  • 21. Informative Personas
  • 22. Creating Your Personas Choose a name ( sticky name – alliteration helps ) ------------------------------------------------------------------------------------- Add an image ( a conversation starter ) ------------------------------------------------------------------------------------- Add a description Value from product ( who is this person? ) ( what is our sell? ) - time at job - financial benefit? - knowledge of domain - increased productivity? - FT / PT - fewer steps? - incentives - more fun? - level of engagement - easier to use?
  • 23. Story Maps ( what is the user experience? )
  • 24. Persona Driven Authoring
  • 25. Anatomy of a User Story The What Story – User goals and tasks The Completion Measures Tests – User satisfaction / product value The How Tasks – Design and coding work The Estimates Effort – Consensus of effort to complete tasks Someone doing (or getting) something of value
  • 26. Let’s Jam! ( fearless story jams )
  • 27. Creating Story Maps  Name high level activities for persona ( “what do you do at work?” ) scenarios - business processes  Walk a day in the life for each activity ( “what are the tasks?” ) user stories (user tasks) - sub processes  Back up and re-tell the experience ( “are there any variations?” )
  • 28. Mile wide - inch deep
  • 29. Let’s Map the Point of Sale
  • 30. Maps Guide Discussions
  • 31. A Clever Variation
  • 32. What are your story maps? Activity Task Task Task Task Task Task Task Task Activity Task Task Task Task Task Task Task Task Task Task Back up and find variations & dead ends
  • 33. - what is still missing? - - what are the next steps? -
  • 34. Variations and Value
  • 35. Mapping Variations
  • 36. Other Invesments (backlog items ) Start up costs Environments Work ( nuke and pave ) Architectural Spikes – Technical Debt Infrastructure Work – Non Story Work Visual design Prototypes (paper and other) - Graphics
  • 37. Which tasks are first? Activity Task Task Task Task Task Task Task Task Activity Task Task Task Task Task Task Task Task Task Task What are your priorities?
  • 38. When is value delivered? Activity Task Task Task Task Task Task Task Task Activity Task Task Task Task Task Task Task Task Task Task What are the story tests?
  • 39. Questions ________________________________________ Coaching and Developing Agility david.hussman@devjam.com www.devjam.com © 2010 DevJam - All rights reserved.