A Product Manager’s Guide to Surviving the Big Bang Approach to Agile Transitions
Salesforce.com took a big bang approach to implement a SCRUM method, with huge success. This meant big changes to how Product Managers work, how we interact with the team, and manages dependencies between teams.
No more 200 page functional specs, no more waiting 12-18 months before features got into customers hands. No more changes to the release dates – how do we survive?
How did we learn to write smaller specs, break them into user stories, and prioritize them? While increasing the amount of features released over time and improving quality? Why would we let our customers and partners help us prioritize what we build?
**Some highlights: **
1. Big Bang works
2. Shorter product release cycles
3. How to write smaller specs and start using proto-typing
4. Manage your product backlog
5. Let your customers vote on which features you are building
6. Why usability testing is so important
7. Make sure customers know about your new features – promote our new products
8. How do you measure success of a new product or feature?
Will cover the changes for the Product Managers at salesforce.com, when we implemented SCRUM as a big bang approach. Innovative methods for identifying customer requirements, and how we deliver features from release plan to communicate changes to customers.