So in the last in this series of three pieces of key Agile jargon, we’ll look at a minimum viable product approach, or an MVP, that you can try.
So in the last in this series of three pieces of key Agile jargon, we’ll look at a minimum viable product approach, or an MVP, that you can try.
#3 𝐖𝐡𝐚𝐭’𝐬 𝐚 𝐌𝐢𝐧𝐢𝐦𝐮𝐦 𝐕𝐢𝐚𝐛𝐥𝐞 𝐏𝐫𝐨𝐝𝐮𝐜𝐭 (𝐌𝐕𝐏)?
– It’s about building a version of a product with just enough features that meet a customer’s needs, that they can give feedback on, which will shape the next version.
– Benefits of this approach:
* It’s faster to build the ‘smallest’ version of a product rather than the final one.
* Getting early feedback means the customer inputs into the design, so they get a better quality product at the end.
* Reduces risk and saves time spent fixing issues afterwards.
So that’s the MVP concept. Want to apply it to comms? I’d recommend it! There’s a worked example for comms in the comments.
Links to the previous posts:
– #1 What’s a sprint?
#2 What’s a backlog?