amee product workflow - 2012.08.16
DESCRIPTION
TRANSCRIPT
Product Management at AMEE
Thursday, 16 August 12
Clear, visible process across the company
Measurable value from development
Lightweight, easily adaptable to future change.
Thursday, 16 August 12
Bugs
Ideas DevelopmentPlanning
Roadmap
Measure
Thursday, 16 August 12
Bugs
Ideas DevelopmentPlanning
Roadmap
Ideas
RoadmapCompany strategy, defined in terms of high level requirements, or high level themes for user stories.
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.
BugsDefects in the product as reported by customers or staff, or issues raised by any error logging tools.
Thursday, 16 August 12
Bugs
Ideas DevelopmentPlanning
Roadmap
Planning
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 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 upon by a development team, and delivered.
Thursday, 16 August 12
Bugs
Ideas DevelopmentPlanning
Roadmap
Planning
EstimationMeeting
Developer Review
Thursday, 16 August 12
Bugs
Ideas DevelopmentPlanning
Roadmap
Planning
EstimationMeeting
Developer Review
One developer and the product manager reviews any story or requirement that needs an estimate in this meeting. Together they weed out technical issues, and dependencies before a group estimation, or identify areas that need further definition before estimation is possible.
Thursday, 16 August 12
Bugs
Ideas DevelopmentPlanning
Roadmap
Planning
EstimationMeeting
Developer Review
In an estimation meeting the developers, and the product manager run through the stories and allocate a points value to each story based on perceived difficulty across the whole team.
Thursday, 16 August 12
Bugs
Ideas DevelopmentPlanning
Roadmap
Sprint planning and development
Daily Standup
Sprint planning
Retro-spective
Sprint Demo
Thursday, 16 August 12
Bugs
Ideas DevelopmentPlanning
Roadmap
Sprint planning and 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 development team commit to delivering the work, based on the velocity agreed in the last sprint retrospective.
Daily Standup
Sprint planning
Retro-spective
Sprint Demo
Thursday, 16 August 12
Bugs
Ideas DevelopmentPlanning
Roadmap
Sprint planning and 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?- What are doing today?- What is blocking you?Sprint progress is reviewed, against what was committed to for the sprint.
Daily Standup
Sprint planning
Retro-spective
Sprint Demo
Thursday, 16 August 12
Bugs
Ideas DevelopmentPlanning
Roadmap
Sprint planning and 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 present, to see the requested story delivered.
Daily Standup
Sprint planning
Retro-spective
Sprint Demo
Thursday, 16 August 12
Bugs
Ideas DevelopmentPlanning
Roadmap
Sprint planning and 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 sprint, based on the points delivered, to help plan the next sprint.
Daily Standup
Sprint planning
Retro-spective
Sprint Demo
Thursday, 16 August 12
Bugs
Ideas DevelopmentPlanning
Roadmap
Thursday, 16 August 12
What this looks like in Trello
Thursday, 16 August 12
Bugs
Ideas DevelopmentPlanning
Roadmap
Filing bugsThursday, 16 August 12
Bugs
Ideas DevelopmentPlanning
Roadmap
Inbox Reviewed & needs input Accepted
Bug with description
Thursday, 16 August 12
Bugs
Ideas DevelopmentPlanning
Roadmap
Inbox Reviewed & needs input Accepted
Bug with description, and
steps to reproduce, etc.
Thursday, 16 August 12
Bugs
Ideas DevelopmentPlanning
Roadmap
Inbox Reviewed & needs input Accepted
Bug with description, and
steps to reproduce, etc.
Thursday, 16 August 12
Bugs
Ideas DevelopmentPlanning
Roadmap
Collecting IdeasThursday, 16 August 12
Bugs
Ideas DevelopmentPlanning
Roadmap
Awaiting Review Under review Accepted
Idea from inside the company
External customer request
Ideas come from any where inside, and outside the company
Thursday, 16 August 12
Bugs
Ideas DevelopmentPlanning
Roadmap
Awaiting Review Under review Accepted
Idea from inside the company
External customer request
A product manager works with the originator, to flesh them out.
Thursday, 16 August 12
Bugs
Ideas DevelopmentPlanning
Roadmap
Awaiting Review Under review Accepted
Idea from inside the company
External customer request
When it’s understood, it can be moved to the planning board
Thursday, 16 August 12
Bugs
Ideas DevelopmentPlanning
Roadmap
How the roadmap drives product
Thursday, 16 August 12
To avoid waste, user stories and features only become more detailed and granular as they get closer to development.
Now
Future
Thursday, 16 August 12
Bugs
Ideas DevelopmentPlanning
Roadmap
Q3 Q4 2013
Update sign-in process
Defined and documented API
RAG status on suppliers
Public sign-in for companies
Scope 3 calculation
CRC Reporting
The Roadmap gives a high level view of areas of focus in coming months.
Thursday, 16 August 12
Bugs
Ideas DevelopmentPlanning
Roadmap
Q3 Q4 2013
Update sign-in process
Defined and documented API
RAG status on suppliers
Public sign-in for companies
Scope 3 calculation
CRC Reporting
New cards are created based on these themes in planning
Thursday, 16 August 12
Bugs
Ideas DevelopmentPlanning
Roadmap
Defining deliverable work
Thursday, 16 August 12
DevelopmentPlanning
User story
To Do Spec and dev review UX and Design Ready for Estimation
The aim is to get cards from the left, to the right. Thursday, 16 August 12
DevelopmentPlanning
User story
To Do Spec and dev review UX and Design Ready for Estimation
It’s okay for cards to be sent back and forth between stages if they need further clarification
User story
Thursday, 16 August 12
DevelopmentPlanning
User story
To Do Spec and dev review UX and Design Ready for Estimation
It’s okay for cards to be sent back and forth between stages if they need further clarification
User story
Thursday, 16 August 12
DevelopmentPlanning
User story
To Do Spec and dev review UX and Design Ready for Estimation
It’s okay for cards to be sent back and forth between stages if they need further clarification
User story
Thursday, 16 August 12
DevelopmentPlanning
User story
To Do Spec and dev review UX and Design Ready for Estimation
Cards are ready when they fit the format for a product, are well understood and have clear
measurement criteria
User story
Thursday, 16 August 12
Bugs
Ideas DevelopmentPlanning
Roadmap
Delivering the work
Thursday, 16 August 12
Estimated
A user story
Current sprint In Progress Pull Request QA Complete
A second story
A user story
A second story
Prioritising estimated storiesThursday, 16 August 12
Estimated
A user story
Current sprint In Progress Pull Request QA Complete
A user story
A second story
A second story
Building a sprint, based on velocity
Thursday, 16 August 12
Estimated
A user story
Current sprint In Progress Pull Request QA Complete
A user story A second story
A second story
Picking up work from the current sprint backlog
Thursday, 16 August 12
Estimated
A user story
Current sprint In Progress Pull Request QA Complete
A user story A second story
A second story
Code review from other developer in pull request
Thursday, 16 August 12
Estimated Current sprint In Progress Pull Request QA Complete
A user story A second story
A second story
QA performed by product owner
A user story
Thursday, 16 August 12
Estimated Current sprint In Progress Pull Request QA Complete
A user story A second story
A second story
Feature ready for release
A user story
Thursday, 16 August 12
Complete
Deployment
A user story
0.17.1
A user story
0.17.2
Bug fix
Completed features by this point should be in a state to be deployed to production.
Depending on the business need, they can be pushed directly to production (in the 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.
User story A another
story
Thursday, 16 August 12
Bugs
Ideas DevelopmentPlanning
Roadmap
Measure
Thursday, 16 August 12
Bugs
Ideas DevelopmentPlanning
Roadmap
Measure
Measuring the value of features
Development doesn’t end at deployment.
Not every feature needs accompanying metrics, but most should have them.
Did a feature have the expected result?
How can we tell?
Are we measuring the right data here?
How might we improve the feature?
How are we getting feedback?
Thursday, 16 August 12
Bugs
Ideas DevelopmentPlanning
Roadmap
Measure
Measuring the value of features
Quantitive Qualitative
Kissmetrics (individual user interactions)
Google Analytics (larger trends, and heatmaps)
Ad-hoc API/DB Queries
In-app chat (eg. Olark)
Support software (desk.com)
User testing (recording how features are used in beta / testing)
Problem & solution interviews ( showing prototypes to users before building)
Thursday, 16 August 12