The Latest
Growing Pains: Why Scaling Scrum and XP Hurts - and What You Can Do[presentation] Do you have a large scale program with multiple agile teams? |
Ed Kraay, SolutionsIQ
|
|
Instill Scrum Values to Build High-Performance Teams[presentation] Your teams are using agile practices well and starting to understand the principles behind them, but they are still not high-performing. |
Lyssa Adkins, Cricketwing Consulting
|
|
CMMI or Agile: Why Not Embrace Both?[presentation] Agile development methods and CMMI® best practices are often perceived to be in conflict with each other. Some even argue that the Agile Manifesto was largely a counter response to the original CMM®. |
Hillel Glazer, Entinex, Inc.
|
|
Determining Business Value[presentation] Agility focuses on delivering business value to the customers as rapidly as possible, and user stories are a common way to describe the features and functions that define value incrementally. |
![]() |
|
Dealing With Defects: The Agile Way[presentation] In agile development, software defects are everyone's responsibility. One tenet of agile is that defects should be fixed "as soon as possible" rather than documented as an inventory of "stuff" that doesn't work yet. |
![]() |
|
Agile Development Practices 2009: The Power of Retrospectives[presentation] One principle in the Agile Manifesto states, "At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly." Retrospectives are a powerful, repeatable tool to help your team continuo |
![]() |
|
Agile Development Practices 2009: Rightsizing Your Project in a Down Economy[presentation] In tough times, both shoes drop simultaneously and "scarcity thinking" takes over in senior executives, managers, and development teams. |
![]() |
|
Debug Your Mind[presentation] Every day, we make important decisions and try to solve critical problems in our work. Unfortunately, our decision-making and problem-solving processes often are based on a faulty memory and our emotional state at the time. |
Andrew Hunt, Pragmatic Programmers
|
|
User Stories for Agile Requirements[presentation] Expressing requirements as user stories is one of the most broadly applicable techniques introduced by the agile processes. |
Mike Cohn, Mountain Goat Software
|
|
Agile Development Practices 2009: Seven Key Factors for Agile Testing Success[presentation] Agile development presents unique challenges for testers and test teams. Working in short iterations, often with limited written requirements, agile development teams can leave traditional testers behind. |
![]() |
|
Small is Beautiful: Business Agility Through Adaptive Governance[presentation] In this economic downturn, is your company looking beyond knee-jerk cost cutting to focus on creative ways to solve business problems? |
![]() |
|
The Scrum Product Owner Demystified[presentation] A Scrum product owner's job is challenging, to say the least. Unfortunately, the specific concepts and techniques required to succeed often aren't spelled out in books and training classes. |
![]() |
|
Sustaining an Agile Culture[presentation] In Scrum, the product owner manages the product backlog-seems simple enough. But what principles are required to make seemingly straightforward agile practices really work? |
![]() |
|
Navigating Conflict on Agile Teams: Why "Resolving" Conflict Won't Work[presentation] On many agile development teams, conflict lurks under the surface and can erupt as a volcano of destruction and suffering. On many agile teams, conflict is viewed mostly as a distraction that keeps the team from getting the job done. |
Lyssa Adkins, Cricketwing Consulting
|
|
Agile Brushstrokes: The Art of Choosing an Agile Transition Style[presentation] Agile software processes vary in detail, depth, impact and endurance as much as painting styles like graffiti differ from Baroque or Impressionist art. What can artists teach us about successful agile transitions? |
Joshua Kerievsky, Industrial Logic
|