Creating a planning culture for distributed agile
- 1. Creating a Planning Culture for Distributed Agile
- 2. Who We Are Modus Create is a Product Studio. We are a global team of product managers, UX designers, and technologists focused on mobile and cloud based apps. We have over 75 people in 14 countries. Our engagements focus on the best engineering talent, the best UX and design, and the best management process to build great apps. Modus Create - Company Overview
- 4. The Right Process Serves the Team AND Serves the Customer
- 6. Sprint Zero We Walk Before We Run
- 7. Team Role Definition PM Front End Backend Proxy to the Product Owner Discovery and analysis User Story writing Defines Acceptance Criteria Manages Product Backlog Manages Product Roadmap Maintains Risk Log Defines Communication Plan and Meetings ScrumMaster for agile process Facilitates Sprint Planning, DSU, UAT, Retrospectives, Story Grooming Business Analysis Issue escalation Product Architect Mitigates technical risk Sizes user stories Performs Code Reviews Ensures coding best practices Contributes to development of complex features Develops features for front-end of application Cordova CSS Sizes User Stories TL/Architect Develops features for backend of application for server side and database API Development Sizes User Stories DevOps Configuration management Development Environments Production Environments Continuous deployment Release management 3rd party app integrations Environment virtualization Sizes User Stories Directions: Fill out the responsibilities of each team role. Example responsibilities listed below.
- 8. Team Role Definition QA UX Prod Owner Regression and automation Manual testing Bug writing Test cases QA Process Owner Low fidelity wireframes High fidelity wireframes Customer surveys Client surveys Design patterns Personas Clickable Mockups User workflows Style guides Low fidelity wireframes High fidelity wireframes Visual Design Client owner of product vision and requirements Communicates vision and details to Product Manager. Client PM Stakeholder Client participants that influence product and business goals and roadmap. Subject matter expert Client sales and marketing Client business owner Client investor Directions: Fill out the responsibilities of each team role. Example responsibilities listed below.
- 10. Directions: Define communication rules for the project Examples: 1. Requirements and prioritization may not be communicated to the team through email. 2. Only the Development team speaks during DSU’s 3. In-person > Google Hangout > GTM > Phone > HipChat > Email 1. __________________________________________________________________________ 2. __________________________________________________________________________ 3. __________________________________________________________________________ 4. __________________________________________________________________________ 5. __________________________________________________________________________ 6. __________________________________________________________________________ Communication Rules
- 11. Communication Plan Meeting _________________ _________________ _________________ _________________ _________________ _________________ Attendees _________________ _________________ _________________ _________________ _________________ _________________ Frequency _________________ _________________ _________________ _________________ _________________ _________________ Date/Time _________________ _________________ _________________ _________________ _________________ _________________ Attendees Everyone The Dev Team Everyone The Dev Team The Dev Team PM, PO, PM,PO, UX Frequency Sprint 0, Sprint 4, ad hoc Every two weeks Every two weeks Every day Every two weeks Minimum of once/Sprint Ad hoc Date/Time 5/29/15, 8:30 AM Fridays, 11:00 AM Fridays, 9:00 AM Daily 9:00 AM Fridays, 8:00 AM Tuesdays, 2:00 PM Thursdays, 2:00 PM Meeting Release Planning Sprint Planning User Acceptance Testing Daily Standup Retrospective Story Grooming UX and Discovery Example Plan Below Directions: Fill out meeting plan for the Release.
- 12. Less than 10% of each Sprint should be in meetings.
- 13. Technology Stack DevOps QA Front End Server Side Vagrant Docker Grunt Circle CI Jenkins Test Flight HockeyApp Heroku Chef/Puppet Cucumber Watir Protractor Sencha AngularJS Cordova React JS Native iOS Native Android JAVA PHP NODE DecafJS .Net Directions: Fill out each box with the tech stack to be used for the product.
- 14. Architecture Diagram Directions: Draw a representation of the end-to-end architecture.
- 15. QA Plan Sample This sample process was based on using Github and pull requests, and leveraging a Tech Lead to review pull requests.
- 16. Writing User Stories Title: As a ____ I want to ____ so that ________ Acceptance Criteria: Given And Or When And Or Then Description: A paragraph or less to describe the business context of the user story, and how this fits into the product roadmap. Theme: Label the Epic/Activity the story falls into Directions: Fill out the details of your candidate user stories.
- 17. Writing Bugs Observed Behavior: 1. Step 1 2. Step 2 3. Step 3 4. Step 4 5. Step 5 6. etc Expected Behavior: Explanation of what the application should do. Bugs should be filled out only AFTER a story has been accepted. If a bug pertains to a story not yet accepted than the story should be rejected, with the issue details commented in the story. If bugs are found after a story has been accepted then the bug should be documented with Observed and Expected Behavior, and the bug should also have an attachment with a gif or screencast to help the developer identify the root cause quickly.
- 18. Managing Scope Creep Directions: Validate whether or not a new feature belongs in the product backlog or the icebox using the following Lean analytics questions:
- 19. Risk Log Risk 1. Not enough time with Product Owner ______________________________ ______________________________ ______________________________ ______________________________ ______________________________ Description User Stories do not have adequate detail for dev team ______________________________ ______________________________ ______________________________ ______________________________ ______________________________ Mitigation Strategy Product Owner to have standing hour long meeting twice a week for story grooming ______________________________ ______________________________ ______________________________ ______________________________ ______________________________ Date Logged 4/8/15 _____________ _____________ _____________ _____________ _____________ Risk Level High _____________ _____________ _____________ _____________ _____________ Directions: Product Manager to fill out risk log throughout the project and review at least once a Sprint with Product Owner to identify and mitigate issues.
- 20. ● One Metric That Matters (OMTM) ○ Optimizing for speed of delivery to market ○ Optimizing for competitive feature ○ Optimizing for technology advantage ○ Optimizing for growth of users ○ Optimizing for revenue capture Release Goals Business Goals Tech Goals Team Goals Non-GoalsProduct Goals Release Metrics Directions: Fill out goals and metrics for this product release. This page will be used as a decision framework for scope prioritization or feature changes during Story Grooming.