Better adoption Prototyping into my teams backlog
Hi there!
I hope someone can help me please :)
So the use of prototyping is a great way of enabling teams to determine the feasibility of upcoming work faster and for them to change direction and pivot a lot faster too. What sort of way do you think teams could better adopt prototyping into their backlog without negatively impacting all the strategic work that they need to deliver?
Thanks so much
Megs
In Scrum, each Sprint is a learning experiment through which MVPs may be validated. An agile organization is a learning organization, and the validated learning never stops.
When innovation is how you roll, is there a meaningful distinction that can be drawn between "prototyping" and "strategic work" at all?
Prototyping allows for quicker learning and reacting. Every Sprint is a time boxed event for the purpose of learning and reacting. Some prototypes will be delivered to the customer while additional work is carried out. Some Product Increments will be delivered to the customer while additional work is carried out.
So, I really don't see why anything special must be done to incorporate prototyping into the Scrum framework.