SVENShorter Time to MarketAlways software to releaseKnow what the customer wants and build it in short timeboxesBe able to flexibly respond to changing demands and market requirements
Create a complete product visionBox for the softwareElevator pitchClear strategy, major featuresEveryone knows what the target is
Brainstorming for all featuresPersonas to get a user flowCreate complete user flows per personaUse that to help Release Planning
Clear longterm targetVision consists of several releasesOnly content of current release is clear
Start with the most important Feature/EpicBreak it down to user storiesBreak user Stories down to smaller User StoriesBefore working on User Stories break them down to Tasks
Too much to do in generalInstead of that is our release date and those features have to be done by then we work on one feature after another and finish them
There is exactly one Priority oneThere is only one priority twoOnce the first ten Priorities are set, the rest isn’t that important anymoreIt’s quite difficult to prioritizeTalking with the team and finding out about critical problems and unknown territory helpsCost of Delay can be a great help
LUISWritinga good backlog with good User Stories requires hard workUser Stories should always be framed in the view of a user of the systemUnexperienced Product Owners need help from coaches or trainings
Independence means that a story can be developed, tested, and potentially even delivered on its own. Therefore, it can also be independently valued.
Product OwnerThe Role of a Product Owner in Scrum
The User Story• As a <role>, I can <activity> so that <business value> where:• ‹ ‹ <role> represents who is performing the action or perhaps one who is receiving the value from the activity. It may even be another system, if that is what is initiating the activity.• ‹ ‹ <activity> represents the action to be performed by the system.• ‹ ‹ <business value> represents the value achieved by the activity.
INVEST or good User Stories Independent Negotiable Valuable Small Estimable Testable
Example• As an administrator, I can set the password expiration period so that users are forced to change their passwords periodically.• As an administrator, I can set the password strength characteristics so that users are required to create difficult-to-hack passwords.
Example for Acceptance CriteriaAs a consumer, I always see current energy pricing reflectedon my portal and on-premise devices so that I know that myenergy usage costs are accurate and reflect any utility pricingchanges.• Conditions of Satisfaction 1. Verify the current pricing is always used and the calculated numbers are displayed correctly on the portal and other on- premise devices (see attachment for formats). 2. Verify the pricing and the calculated numbers are updated correctly when the price changes. 3. Verify the “current price” field itself is updated according the scheduled time. 4. Verify the info/error messages when there is a fault in the pricing (see approved error messages attached).