27. Velocity
We have developed a new portal in just 14
weeks
With Scrum you can be as fast as twice the
speed of waterfall projects
Launch date guarantee, but no scope
guarantee ;)
28. Flexibility
Change the scope without change requests
Dependencies to 3rd party service providers are
easier to manage
29. Quality
The Scrum team feels responsible
Quality remains a team factor from start until
the project ends
30. Transparency
Due to the restrict time boxing Scrum behalves
like a good project plan
Sprint Review Meetings with product demos are
like milestones
Your client is able to speak to the team during
each product demo
The client can talk to the product owner at any
time
32. UX and Scrum
Be creative but do as much as possible in
sprint 0
Three options for UX during Scrum sprits
Integrated UX sprint
Shifted UX sprint
Hybrid UX sprint
33. UX and Scrum
Integrated UX sprint
UX sprint nUX
DEV
Sprint n Sprint n+1
DEV sprint n
UX sprint n+1
DEV sprint n+1
The integrated UX sprint is hard. It puts UX under pressure at the beginning
of each sprint and DEV at the end.
34. UX and Scrum
Shifted UX sprint
UX sprint n+1UX
DEV
Sprint n Sprint n+1
DEV sprint n
UX sprint n+2
DEV sprint n+1
UX runs ahead of DEV by the length of one sprint. This looks and feels like a
small waterfall. More design artifacts may be created than necessary but the
PO gets a chance to get approvals from stakeholders before DEV starts. The
team is working on different stories at the same time which is not optimum for
finding the best solution together.
35. UX and Scrum
Hybrid UX sprint
UX sprint n+1UX
DEV
Sprint n Sprint n+1
DEV sprint n
UX sprint n+2
DEV sprint n+1
We suggest you to try hybrid UX sprints. During the first half of each sprint
UX and DEV are working together on the same stories. During the second
half of the sprint the PO and UX prepare concepts for the planning meeting
of the next sprint, do user tests and so on.
UX sprint n UX sprint n+1
36. Team room
Even if the Scrum project is not the only project
the team members are working for
Reduces setup times and context switches
Boosts team communication
37. Experienced team members
Junior teams may have problems to handle
their degree of freedom
The product vision needs to be clear
Hard acceptance criteria for each story are
helpful
What’s not written in the story doesn’t belong to
the story. Thus it doesn’t need to be done ;)
39. Your backlog is your backlog
In our customer journey workshop we have
collected more than 100 stories. During the
project we have finished a quarter of them.