• Save
Project inception   mke agile june 2013
Upcoming SlideShare
Loading in...5
×

Like this? Share it with your network

Share

Project inception mke agile june 2013

  • 680 views
Uploaded on

Creating a backlog of user stories is pretty straightforward but it doesn’t help you when it comes to decisions like what to build first, how to prioritize and groom the backlog, how to scope and ...

Creating a backlog of user stories is pretty straightforward but it doesn’t help you when it comes to decisions like what to build first, how to prioritize and groom the backlog, how to scope and plan a project, and how to visualize overall progress. This is a big challenge for many agile teams especially when beginning a project. To do this, we need more context.

Personas and story maps are tools that bring the user and their experience to life. They provide context for the work throughout the development stream. Personas generate and capture insight about the customers or users. Story maps are multi-dimensional representations of goals and activities that span the user’s experience from start to finish and become the source for our product backlog. Finer-grained user stories are born from the story map and retain context when flowing through development. This improves the value-based decision making of scoping, prioritizing, planning, and measuring progress through the entire development stream because we have context that ties back to users’ goals and experience.

The session will start with what personas are and how to create them. From there, we will explore the creation of story maps as a group through a real world example. In this collaborative session, attendees will learn new tools for generating a user-centered product roadmap that goes beyond the basic backlog and becomes a solid foundation during the inception of a project.

More in: Business , Technology
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Be the first to comment
No Downloads

Views

Total Views
680
On Slideshare
680
From Embeds
0
Number of Embeds
0

Actions

Shares
Downloads
0
Comments
0
Likes
1

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. © 2012 Redpoint Technologies.All rights reserved.Project Inceptions with Story Maps and PersonasMilwaukee AgileDave Neuman, Principal, Redpoint TechnologiesTuesday, June 11, 2013Confidential information.
  • 2. Our Challenge TodayLaunch a new product in 6 months or less using an Agile delivery approach•  Name:­  TestNation!•  Product:­  Awesome electronic test management and test taking platform for high schools•  Market:­  Over 16M students and over 1M teachers in about 36K secondary schools•  Goals:1.  Save 1 hour of time per test for teachers in manual test creation, grading, and reporting•  1hr x 5 tests x 1M teachers = 5M hrs x $40/hr = $200M in savings that can be spentelsewhere•  1hr x 5 tests x 1M teachers = 5M hrs of additional teaching of students2.  Improve quality and reliability of testing results (limit cheating and favoritism)2
  • 3. Our Challenge TodayLaunch a new product in 6 months or less and delivery needs to be Agile•  Name:­  TestNation!•  Product:­  Awesome electronic test management and test taking platform for high schools•  Market:­  Over 16M students and over 1M teachers in about 36K secondary schools•  Goals:1.  Save 1 hour of time per test for teachers in manual test creation, grading, and reporting•  1hr x 5 tests x 1M teachers = 5M hrs x $40/hr = $200M in savings that can be spentelsewhere•  1hr x 5 tests x 1M teachers = 5M hrs of additional teaching of students2.  Improve quality and reliability of testing results (limit cheating and favoritism)3Where do we start?
  • 4. Typical Project Inception Flow4ProjectCharterDeliveryProductRoadmapDeliveryPMSponsorProductManagerTeam(s)Team(s)RequirementsSprint 0BlitzPlanningSprint 0SpecsLeanStartupBuild a minimalviable productBacklogTeamCustomerDevelopment
  • 5. Typical Project Inception Flow5ProjectCharterDeliveryProductRoadmapDeliveryPMSponsorProductManagerTeam(s)Team(s)RequirementsSprint 0BlitzPlanningSprint 0SpecsLeanStartupBuild a minimalviable productBacklogTeamCustomerDevelopmentWhere is the customer oruser in the process?
  • 6. Integrate User Centered Design into Project Inceptions = Success6ProductVisioningUserProfilingStoryMappingAgileDeliveryCross-functional Inception Team – Customer, users, delivery team, product/project mgmtDelivery Teams•  Drives more user experience and product-centric design thinking before delivery begins•  Provides rich context to guide planning, feature prioritization, and development decisions•  Tools for entire team to UNDERSTAND THE BIG PICTUREBacklog ofFeatures~ 2-5 Days from start to finishProblem / SolutionBusiness ModelBusiness CaseProject CharterPersonasStoryMaps
  • 7. Integrate User Centered Design into Project Inceptions = Success7ProductVisioningUserProfilingStoryMappingAgileDeliveryCross-functional Inception Team – Customer, users, delivery team, product/project mgmtDelivery TeamsPersonasStoryMaps•  Drives more user experience and product-centric design thinking before delivery begins•  Provides rich context to guide planning, feature prioritization, and development decisions•  Tools for entire team to UNDERSTAND THE BIG PICTUREProblem / SolutionBusiness ModelBusiness CaseProject CharterBacklog ofFeatures~ 2-5 Days from start to finish
  • 8. Why Personas•  Needs­  Quick way to develop a customer or user profile­  Go beyond basic demographics­  Develop shared understanding of users environment, behavior,concerns, and motivations•  Positive Outcomes­  Make the user and their experience a 1st class citizen­  Guide decision making in business models, product roadmaps,projects, product backlogs, UX design, etc.8
  • 9. Persona Development using Empathy Maps9Six questions toquickly profile acustomer or userDeveloped byScott Mathews of XPLANE
  • 10. Let’s ProfileProfile one TestNation! user using an Empathy Map1.  2 min – Generate list of possible users and select one to profile2.  2 min - Individually brainstorm one comment for each question SILENTLY3.  3 min - When everyone is ready then take turns adding comments to the map(consolidate similar comments into one comment)4.  3 min – Give the persona a name, read out the profile within group for confirmation5.  10 min total10
  • 11. Show and tell, persona styleWould one persona please stand-up and introduce themself11
  • 12. User Story Maps•  A collection of user stories is a product backlog•  A user story map is an approach to ORGANIZING and PRIORITIZING userstories using a multi-dimensional arrangement of goals, activities, and stories•  Positive Outcomes­  Makes end to end user experience or workflow visible­  Show relationships between larger stories to smaller stories as well as alternatevariations and alternate flows­  Confirm completeness of the backlog­  Context for prioritization and release planning that focuses on goals and activities­  Team’s own visual language for big picture thinking and context12
  • 13. User Story Maps - Described13TimeReleases PriorityHighLowVariationsVariationsUser ActivitiesUser StoriesTell the big story of the product – a day in the life of a userUser GoalsWalkingSkeleton
  • 14. User Story Maps – Described with examples14TimeReleases PriorityHighLowVariationsVariationsUser ActivitiesUser StoriesTell the big story of the product – a day in the life of a userUser Goals OrganizeEmailManageEmailCreateBasicOpenBasicDeleteEmailOpenHTMLCreateHTMLManageCalendarMarkReadWalkingSkeletonComposeEmailReadEmailDeleteEmailSearchEmailFileEmailsArchiveEmail(begin with verbs)
  • 15. User Story Maps - Advanced15TimeUser GoalsUser ActivitiesUser Stories Releases PriorityHighLowVariationsVariationsUI MockupsOrganizeEmailManageEmailCreateBasicOpenBasicDeleteEmailMarkReadOpenHTMLCreateHTMLManageCalendarSystemActionWalkingSkeletonComposeEmailReadEmailDeleteEmailSearchEmailFileEmailsArchiveEmail
  • 16. User Story Maps – Real World Example16
  • 17. Let’s PracticeCreate a Story Map for your TestNation! solution using your persona1.  5 min – Silent Brainstorming•  Individually brainstorm user activities SILENTLY (be sure to sequence them in order)•  Ask yourself, “How does the user X accomplish Y goal? What are the steps theytake?”2.  10 min – Collaborative walking skeleton•  When everyone is ready then take turns placing cards on the table beginning with firstin sequence•  Consolidate similar cards into one card, throw out duplicates•  Group activities and identify the goals for those activities placing a goal card at the top3.  5 min – Alternate pathing•  Find alternate variations by walking the process and asking, “What else could theydo?”17
  • 18. Walking skeleton report outTell us the story of your TestNation! solutionfrom the perspective of your persona18
  • 19. Wrap-upAny questions?Thank you!19