Role definition and change management are the most difficult obstacles to overcome for large organizations that adopt Agile. Employees can feel threatened and pushed out of their comfort zone by the barrage of changes—from the process they use, to the changes in titles, the reporting structure, and the focus on results versus risk mitigation. This article explores how best to facilitate role changes during an agile transformation.
Have you had the same requirements-gathering discussion multiple times but still don’t know what to do next? Does your team shudder when they see you break out sticky notes in a meeting? (Hint: If you answered yes to either of these questions, keep reading) Practice the five skills outlined in this post for effective workshop facilitation.
When developing a product, it’s important to build things the right way—high-quality code that’s tightly aligned to requirements. But even perfectly built software is worthless if it has no value to the end user. That’s where results-driven development comes in. We explore how to build products the right way, while making sure we're building the right products.
The concept of Dual-Track Scrum was first evangelized by Marty Cagan back in 2012, and more recently elements of it have been incorporated into Google's Design Sprint. We recently wrote about how Dual-Track works from a design perspective, and want to demonstrate how it can be applied in practice. By leveraging Dual-Track Scrum, teams are more focused, reduce their rework and significantly improve their ability to plan while still retaining their agility. In this article, we'll review the benefits of Dual-Track Scrum and show how we implement it in practice using agile tools.