Hello again from BAMTECH Media and our Project Management Team. Welcome to this, our one hundredth edition of “This Week in #Agile”. Please feel free to peruse some of the articles that we’ve enjoyed reading over the past week.
If you work in a Scrum team, you undoubtedly know that you should have a product backlog and product owner; but what, exactly, is a product?
For some teams, this can be a rather fundamental question, after all, an organization cannot identify appropriate product owners, teams and roles without first knowing what its products are. If there is to be one product backlog per product, we need to know what our products are before creating a product backlog for each.
Value stream mapping is a way to find waste in process; I have seen many complex examples. I like Jay’s approach. It is simple and will allow you to quickly find the low hanging fruits.
Stuffing agile down people’s throats will, at best, get you compliance. John reminds us that we have to show the benefits of each change that we suggest, changing one baby step at a time.
An agile team should maintain a consistent sprint length; unfortunately, when I first began doing iterative and incremental development (even a bit before doing what today we’d call agile development), I made the mistake of not having all of our sprints be the same length.
Sprint planning is a key ceremony within your team's Scrum cadence. The 4 steps that Dan explains in his blog will give you a greater chance of having a successful planning session. There are also a few bonus examples, and animated examples regarding how to fully execute functions on Jira.
Here at Bamtech we love catching up with people's opinions and articles, so please do not hesitate to get in touch if you have something to share. You can contact us via email on Scott.Kirkbright@bamtechmedia.com or on twitter @Scottkirkbright
Many thanks to Ryan Key for this week’s image.
If you're interested in careers at Cake and BAMTECH Media then head over to our careers page to check them out.