Velocity We have developed a new portal in just 14weeks With Scrum you can be as fast as twice thespeed of waterfall projects Launch date guarantee, but no scopeguarantee ;)
Flexibility Change the scope without change requests Dependencies to 3rd party service providers areeasier to manage
Quality The Scrum team feels responsible Quality remains a team factor from start untilthe project ends
Transparency Due to the restrict time boxing Scrum behalveslike a good project plan Sprint Review Meetings with product demos arelike milestones Your client is able to speak to the team duringeach product demo The client can talk to the product owner at anytime
UX and Scrum Be creative but do as much as possible insprint 0 Three options for UX during Scrum sprits Integrated UX sprint Shifted UX sprint Hybrid UX sprint
UX and ScrumIntegrated UX sprintUX sprint nUXDEVSprint n Sprint n+1DEV sprint nUX sprint n+1DEV sprint n+1The integrated UX sprint is hard. It puts UX under pressure at the beginningof each sprint and DEV at the end.
UX and ScrumShifted UX sprintUX sprint n+1UXDEVSprint n Sprint n+1DEV sprint nUX sprint n+2DEV sprint n+1UX runs ahead of DEV by the length of one sprint. This looks and feels like asmall waterfall. More design artifacts may be created than necessary but thePO gets a chance to get approvals from stakeholders before DEV starts. Theteam is working on different stories at the same time which is not optimum forfinding the best solution together.
UX and ScrumHybrid UX sprintUX sprint n+1UXDEVSprint n Sprint n+1DEV sprint nUX sprint n+2DEV sprint n+1We suggest you to try hybrid UX sprints. During the first half of each sprintUX and DEV are working together on the same stories. During the secondhalf of the sprint the PO and UX prepare concepts for the planning meetingof the next sprint, do user tests and so on.UX sprint n UX sprint n+1
Team room Even if the Scrum project is not the only projectthe team members are working for Reduces setup times and context switches Boosts team communication
Experienced team members Junior teams may have problems to handletheir degree of freedom The product vision needs to be clear Hard acceptance criteria for each story arehelpful What’s not written in the story doesn’t belong tothe story. Thus it doesn’t need to be done ;)
More small stories A story shouldn’t be larger than the teamvelocity.
Your backlog is your backlog In our customer journey workshop we havecollected more than 100 stories. During theproject we have finished a quarter of them.