Related Content
Which Delivery Option Is Right for Your New Agile Program? With agile, you have delivery model options you didn’t have before. You can do continuous deployment or phased deployment, or stick with a traditional rollout. There is no hands-down best model. What you choose should depend on what your team and your customers need. Here's how to figure that out. |
||
Do Agile Teams Really Need Managers? Steve Berczuk explores whether or not we really need managers in an agile team. Managers perform a variety of functions that are useful for self-organizing teams. The challenge is how to perform those functions effectively while keeping with the spirit of self-organization. |
||
When Managing Multiple Teams, Think Networks—Not Hierarchies The more complex your program, the harder it is to communicate. But contrary to some management styles, the larger your program, the less you want a hierarchy. It's better to assemble networks of people equally responsible for their problems. Read on for tips on how to organize for multiple teams. |
||
Why You Need to Take Technical Debt into Account Technical debt is a metaphor for the result of skipping design or the implementation steps in order to achieve a short-term goal. The next time you work with code, remember that changes may be more costly to make because of your prior decisions. You achieved something, but you incurred debt. |
||
Four Steps to Managing Programs with Agile and Traditional Projects You are a program manager with some agile projects and some traditional projects in the midst of an agile transition. How do you manage the program? You have to help the traditional project managers work in some new and different ways. Here are four steps to help the adjustment go more smoothly. |
||
Book Review: The Art of Possibility Steve Berczuk reviews The Art of Possibility by Rosamund Stone Zander and Benjamin Zander. The book will help you learn how to focus on what’s possible given a difficult situation, rather than just concentrating on the current problem. |
||
How Metrics Distract Stakeholders on Agile Software Projects Metrics can be distractions to stakeholders from seeing true value in agile software projects. Stakeholders can gain more realistic insight by observing the intangibles—like accountability, transparency, and trust in teams—rather than just following the numbers on a software project dashboard. |
||
What ALM Tool Features Best Support Agile Software Development? Joe Farah details the key features necessary in application lifecycle management (ALM) tools to make them practical for agile development. At a minimum, agile-friendly ALM tools must support user stories, prioritization, traceability, continuous integration, and metrics for post-iteration analysis. |