Agile Development Methods
 |
Lessons Learned from Product Failures Being agile is all about learning from failures and building on experiences. This applies to not just individuals, but even to large organizations. The key is being transparent and objective in accepting and understanding failures, and taking away lessons for future actions and decisions. Just keep innovating. |
|
 |
Coaching Senior Management to Be Agile Embracing an agile mindset isn’t always easy, and it can be especially difficult for senior managers who spent most of their careers working in more traditional development methodologies. By trying to speak the same language and demonstrating successful self-organization, teams can help senior management become agile. |
|
 |
Building Good Scrum Habits Building good habits is an important part of an effective Scrum team. Habits are a form of automation: The more basic processes we can automate, the more we can focus our energy on hard things. The Scrum process, with its focus on rituals, helps us by providing a framework for collaboration and making it second nature. |
|
 |
Tips for Getting an Agile Transformation Off the Ground Many agile transformations are doomed before they even begin. Organizations focus on the wrong things up front, resulting in a poorly planned effort that doesn’t deliver business value. Here are some tips to get things started the right way, including how to communicate well, define roles, and change your culture. |
|
 |
Rethinking Your Measurement and Metrics for Agile and DevOps In their transition to agile and DevOps, many teams forget they also need to update their measurement and metrics plan. Some measurements and metrics from the traditional waterfall software development lifecycle may remain useful, but many may not provide value—and some may even adversely impact progress toward goals. |
|
 |
Supporting Scrum: Adopt before You Adapt Scrum is a fairly minimal agile process framework that you can adapt to work best for your team. But adaptation works best once the team has internalized the principles and values of the Scrum process, and that takes practice. In other words: Before you start to adapt Scrum, first try fully adopting the framework. |
|
 |
Understanding the ScrumMaster's Role in Team Communication Some agile teams believe the ScrumMaster is the sole point of communication between them and the product owner, so the team can abdicate any responsibility to communicate with stakeholders. That couldn't be more wrong. It's actually the ScrumMaster's job to enable communication and coach or guide the team to solutions. |
|
 |
Agile Dojo: Speed Up Delivery Using Focus An Agile Dojo is an immersive learning experience where teams bring their work into a collocated space and work together to complete a project, using “hyper-iterations” of two-day sprints, over six weeks. Even distributed teams are able to collaborate, focus, and deliver projects on time and within budget. Here's how. |
