9:00 - 10:30 - Scrum Metrics for Hyperproductive Teams: How They Fly Like Fighter Aircraft, Jeff Sutherland et Scott Downey

Mes tweets :

• clean up the product backlog by relying on the INVEST acronym (Independent, Negotiable, Valuable, Estimable, Sized appropriately, and Testable).
• First start with time to fix bugs to get the first X2 productivity
• Sprint planning meeting: anchoring the Scale - using the INVEST & Value, Voice & Visibility
• Changes to Scrum meetings: teams want to start by the easiest story, Scrum Master set the story points at 3! It always work to set the scale
• 3 is OK if user stories are well written. Always true even if not agile (my opinion) but less visible from the beginning
• If a user story is too large to put in a Sprint Backlog, let the user, PO?, break it in terms of business value
• Try RoboCoach (metrics for hyper-productive teams) - http://rapidscrum.com/RoboCoach 

• la vélocité,
• la capacité de travail,
• le facteur de focus (vélocité / capacité de travail ),
• le travail adopté en cours de sprint => encourager l'équipe à s'engager plus
• le travail découvert en cours de sprint => encourager l'équipe à mieux analyser les estimations initiales des stories pour mieux anticiper sous-estimations potentielles
• l'augmentation de value ciblée (valeur de la vélocité du sprint courant / la vélocité originale)
• l'exactitude des estimations,
• l'exactitude des engagements de l'équipe

• Using Collaborative Product DIscovery to Plan Agile Projects
• How do you decide what to build? How do you know when you are ready to start building?
• Discovery: understand the right product to build vs Delivery: build the product right -> find the right balance
• Learn about the context to identify the solution: context in terms of business strategy, user goals, Product usage, Regulatory constraints
• Target solution to maximise outcome, not output: starting context -> ideas (features, ...) -> incremental dev -> delivery :-)
• Resulting context -> outcome is user happy with the output of the incremental dev.
• User really happy -> great impact in the resulting context
• Try more to maximise outcome than output -> fit to the user expectations in the resulting context
• Prioritize outcomes, not outputs
• Use Workshops for effective collaboration with larger groups: understand purpose, customers and users of products
• Don't hesitate to use videos to explain ideas in distribued teams
• Use story map & storyboard to collaboratively discover product - then simulate use !!!!
• Slice the backlog into incremental releases with "goals"

• RT @estherderby: containers, difference , exchanges: structures that drive behavior in organizations. http://bit.ly/j8pyv
• RT @estherderby: every team is self-organizing within their constraints. trick is neither over nor underconstraining the team.
• Scrum Masters think about a project as a 1 hour race, project managers as a 10k race!

• Concept -> ideas -> main features -> features + screens -> cost -> user stories
• Use Case still interesting to capture features !
• From features to user stories? Paper storyboard of the project to derive story cards (usages of the app)
• Clarify requirements with Story Tests - success & failure paths