How to identify ‘bad agile smells’

MediumAs someone who has been on the front lines of agile and scrum practices inside government, Mark Vogelgesang, Innovation Specialist at the GSA, explains some of the common bad habits agencies must guard against.

From scope creep to long deployments, there are many possible bumps in the road to a great agile process – but there are also practical solutions. One example is the miscommunication that may occur between developers and product owners, leading an end product that is different than expected.

To mitigate this risk, ask your development team during the sprint planning meeting to explain the business problem back to you using simplified language. If the team is having trouble re-explaining the business requirement, that’s a good sign there is a gap in communication. Additionally, have developers bring you into the review process while they are coding. Remember, a story is a promise to have a conversation — it is not the end of the conversation about the feature.

Read the full article: When good scrum goes bad – identifying bad agile smells | Mark Vogelgesang, via Medium

2017-04-23T23:02:29+00:00 January 11th, 2017|Categories: AGL Community|Tags: |

About the Author:

Agile Government Leadership is a community-powered network of agile government professionals. Subscribe to our newsletter or connect on LinkedIn and Twitter.

Leave a Reply