Their customers were frustrated with how long it took to address simple bug reports and for their requested enhancements to be delivered. Stakeholders were unhappy and felt like their requests mostly went into a black hole. On top of that, stakeholders’ requests regularly were in conflict. Lead time was high for any request that was not an emergency, and firefighting was all too common. Although stakeholders were aware that the development team pulled items from the backlog only when they became available, stakeholders still felt abandoned and ignored. At the same time, the stakeholders, who were all account managers and worked directly with end users, continued to request feature enhancements to satisfy the customers they represented. There was a great deal of technical debt to pay down, which stifled the team’s ability to make improvements and proceed with their planned sprints. However, progress was very slow because developers were busy with product feature enhancements and bug fixes. The development team and the architects had set a challenging goal to move the product to a cloud-based platform. A company’s product team found itself in a problematic situation with the company’s flagship product. In this intensive session, all the stakeholders can work together to agree on a plan that charts the path forward. To bridge this division and save time, the best solution is a prioritization workshop that enables them to come to a consensus on the relative priority of their requests. The result is often wasted time and resources. However, it can get overwhelming when there are multiple stakeholders: They all make requests independent of one another and asynchronously, while the product manager spends long hours in one-on-one meetings, negotiating with them over what items will make it into the next sprint. Backlog prioritization is a key component of agile product development.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |