Amee product development workflow
Upcoming SlideShare
Loading in...5
×
 

Amee product development workflow

on

  • 374 views

A draft

A draft

Statistics

Views

Total Views
374
Views on SlideShare
374
Embed Views
0

Actions

Likes
0
Downloads
5
Comments
0

0 Embeds 0

No embeds

Accessibility

Categories

Upload Details

Uploaded via as Adobe PDF

Usage Rights

CC Attribution-ShareAlike LicenseCC Attribution-ShareAlike License

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

Amee product development workflow Amee product development workflow Presentation Transcript

  • Product Management at AMEEFriday, 26 October 12
  • Clear, visible process across the company Measurable value from development Lightweight, easily adaptable to future change.Friday, 26 October 12
  • Bugs Ideas Planning Development Measure RoadmapFriday, 26 October 12
  • Bugs Bugs Defects in the product as reported by customers or staff, or issues raised by any error logging tools. Ideas Ideas Planning Development Suggestions for the product come from inside the company, or from external sources, like customer service channels, or any external forums for discussion of the product. Roadmap Roadmap Company strategy, defined in terms of high level requirements, or high level themes for user stories.Friday, 26 October 12
  • Planning Bugs Input from each board has a qualifying process before it makes it to planning. Bugs are confirmed as reproducible, Ideas are described in enough detail to be Ideas Planning Development understood by a product manager Items on the roadmap are confirmed as still relevant to the company strategy. Requirements or draft stories are fleshed out here, with sketches or wireframes, until they are in a state that can be estimated Roadmap upon by a development team, and delivered.Friday, 26 October 12
  • Planning Bugs Developer Estimation Review Meeting Ideas Planning Development RoadmapFriday, 26 October 12
  • Planning Bugs Developer Estimation Review Meeting Ideas Planning Development One developer and the product manager reviews any story or requirement that needs an estimate in this meeting. Roadmap Together they weed out technical issues, and dependencies before a group estimation, or identify areas that need further definition before estimation is possible.Friday, 26 October 12
  • Planning Bugs Developer Estimation Review Meeting Ideas Planning Development In an estimation meeting the developers, and the product manager run through the stories and allocate a points value to Roadmap each story based on perceived difficulty across the whole team.Friday, 26 October 12
  • Sprint planning and development Bugs Sprint Daily Sprint Retro- planning Standup Demo spective Ideas Planning Development RoadmapFriday, 26 October 12
  • Sprint planning and development Bugs Sprint Daily Sprint Retro- planning Standup Demo spective Ideas Planning Development Stories and requirements are assigned to a sprint in a sprint planning meeting. A product manager reviews the stories going into the sprint with the development team, and the Roadmap development team commit to delivering the work, based on the velocity agreed in the last sprint retrospective.Friday, 26 October 12
  • Sprint planning and development Bugs Sprint Daily Sprint Retro- planning Standup Demo spective Ideas Planning Development Every morning, the development team and the product manager runs a 15 min stand-up meeting, answering the following questions: - What you did yesterday? Roadmap doing today? - What are - What is blocking you? Sprint progress is reviewed, against what was committed to for the sprint.Friday, 26 October 12
  • Sprint planning and development Bugs Sprint Daily Sprint Retro- planning Standup Demo spective Ideas Planning Development On the last day of the sprint, the team members run through the work they’ve completed to the rest of the team, and the product manager. Original ‘owners’ of an idea are optionally Roadmap to see the requested story delivered. present,Friday, 26 October 12
  • Sprint planning and development Bugs Sprint Daily Sprint Retro- planning Standup Demo spective Ideas Planning Development After the sprint demo, comes the retrospective. The team discusses the good and bad aspects of the sprint, and any changes to their process they’d like see internally. The team commit to a velocity for the next Roadmap sprint, based on the points delivered, to help plan the next sprint.Friday, 26 October 12
  • Bugs Ideas Planning Development RoadmapFriday, 26 October 12
  • What this looks like in TrelloFriday, 26 October 12
  • Bugs Ideas Planning Development Roadmap Filing bugsFriday, 26 October 12
  • Reviewed & Inbox Accepted needs input Bugs Bug with description Ideas Planning Development RoadmapFriday, 26 October 12
  • Reviewed & Inbox Accepted needs input Bugs Bug with description, and steps to reproduce, etc. Ideas Planning Development RoadmapFriday, 26 October 12
  • Reviewed & Inbox Accepted needs input Bugs Bug with description, and steps to reproduce, etc. Ideas Planning Development RoadmapFriday, 26 October 12
  • Bugs Ideas Planning Development Roadmap Collecting IdeasFriday, 26 October 12
  • Awaiting Review Under review Accepted Bugs Idea from inside the company Ideas Planning External customer Development request Roadmap Ideas come from any where inside, and outside the companyFriday, 26 October 12
  • Awaiting Review Under review Accepted Bugs Idea from inside the company Ideas Planning External customer Development request Roadmap A product manager works with the originator, to flesh them out.Friday, 26 October 12
  • Awaiting Review Under review Accepted Bugs Idea from inside the company Ideas Planning External customer Development request Roadmap When it’s understood, it can be moved to the planning boardFriday, 26 October 12
  • Bugs Ideas Planning Development Roadmap How the roadmap drives productFriday, 26 October 12
  • Now To avoid waste, user stories and features only become more detailed and granular as they get closer to development. FutureFriday, 26 October 12
  • Q3 Q4 2013 Bugs Update sign-in Public sign-in for Scope 3 process companies calculation Ideas Defined and Planning Development documented API CRC Reporting RAG status on Roadmap suppliers The Roadmap gives a high level view of areas of focus in coming months.Friday, 26 October 12
  • Q3 Q4 2013 Bugs Update sign-in Public sign-in for Scope 3 process companies calculation Ideas Defined and Planning Development documented API CRC Reporting RAG status on Roadmap suppliers New cards are created based on these themes in planningFriday, 26 October 12
  • Bugs Ideas Planning Development Roadmap Defining deliverable workFriday, 26 October 12
  • Ready for To Do Spec and dev review UX and Design Estimation User story Planning Development The aim is to get cards from the left, to the right.Friday, 26 October 12
  • Ready for To Do Spec and dev review UX and Design Estimation User story User story Planning Development It’s okay for cards to be sent back and forth between stages if they need further clarificationFriday, 26 October 12
  • Ready for To Do Spec and dev review UX and Design Estimation User story User story Planning Development It’s okay for cards to be sent back and forth between stages if they need further clarificationFriday, 26 October 12
  • Ready for To Do Spec and dev review UX and Design Estimation User story User story Planning Development It’s okay for cards to be sent back and forth between stages if they need further clarificationFriday, 26 October 12
  • Ready for To Do Spec and dev review UX and Design Estimation User story User story Planning Development Cards are ready when they fit the format for a product, are well understood and have clear measurement criteriaFriday, 26 October 12
  • Main goals for dev process Simplicity Transparency FlexibilityFriday, 26 October 12
  • Bugs Ideas Planning Development Roadmap Delivering the workFriday, 26 October 12
  • Estimated Current sprint In Progress Pull Request QA Complete A user story A second story A user story A second story Prioritising estimated storiesFriday, 26 October 12
  • Estimated Current sprint In Progress Pull Request QA Complete A user story A user story A second A second story story Building a sprint, based onFriday, 26 October 12 velocity
  • Estimated Current sprint In Progress Pull Request QA Complete A second A user story A user story story A second story Picking up work from theFriday, 26 October 12 current sprint backlog
  • Estimated Current sprint In Progress Pull Request QA Complete A second A user story A user story story A second story Code review from otherFriday, 26 October 12 developer in pull request
  • Estimated Current sprint In Progress Pull Request QA Complete A second A user story A user story story A second story QA performed by productFriday, 26 October 12 owner
  • Estimated Current sprint In Progress Pull Request QA Complete A second A user story A user story story A second story Feature ready for releaseFriday, 26 October 12
  • Completed features by this point should be in a state to be Complete 0.17.1 0.17.2 deployed to production. A user story A user story Bug fix Depending on the business need, they can be pushed directly to production (in the A another story User story case of severe bugs etc), or as specific releases. The aspiration here is to working, QA’d, and CR’d code automatically pushed to production, where features can be rolled out gradually, or switched on or off independently of code releases. DeploymentFriday, 26 October 12
  • Bugs Ideas Planning Development Measure RoadmapFriday, 26 October 12
  • Measuring the value of features Bugs Development doesn’t end at deployment. Ideas every feature needs accompanying metrics, but Not Planning Development Measure most should have them. Did a feature have the expected result? Roadmap can we tell? How Are we measuring the right data here? How might we improve the feature? How are we getting feedback?Friday, 26 October 12
  • Measuring the value of features Bugs Quantitive Qualitative Ideas Planning In-app chat Development Measure Kissmetrics (eg. Olark) (individual user interactions) Support software (desk.com) Google Analytics Roadmap trends, and (larger heatmaps) User testing (recording how features are used in beta / testing) Ad-hoc API/DB Queries Problem & solution interviews ( showing prototypes to users before building)Friday, 26 October 12