|
The Kanban Primer: A Cultural Evolution in Software Kanban,a Japanese word meaning “signal card,” introduces a new way to think about software development. Through signaling, a limit is set on work in progress resulting in a system that is never overloaded. Kanban signals do not need to be based on passing physical cards; any virtual signaling mechanism will do equally well.
|
|
|
What's a Manager to Do? Self-organizing teams still need managers. But those managers need to rethink how they do their jobs and consider how much self-management the team can take on. Finding the sweet spot between hands on and hands off is the key.
|
|
|
Follow the Process Building better software does not rely on methodologies. "Following the process" omits important human factors that ultimately lead us to success.
|
|
|
Getting Agile With User-Centered Design Agile practices go a long way toward providing value to our customers. But in today's market, we must endeavor to adopt a more user-centered approach to create products our customers can't live without.
|
|
|
Keep Non-developers in the Loop Keeping QA members up to date on changes as they happen–through meetings, wikis, and email–can reduce the number of unnecessary bug reports and save you time and frustration.
|
|
|
Is ''Agile'' Distracting You? If a process tool or service claims to be agile it must be good, right? Not necessarily. The term "agile" has become abused and, since we don't have a standard dictionary definition, it is open to interpretation. So, let's look beyond the label to what really matters—value.
|
|
|
Encourage Pair Programming Pair programming is one of the most controversial agile practices. Managers are concerned about the costs and developers are concerned about personal agony. But there also are many benefits. If you are thinking about trying pair programming, here are several reasons why you should.
|
|
|
How to Fail with Agile A switch to agile often conflicts with personal career goals such as maintaining the status quo and working no harder than necessary. These twenty guidelines will help you sabotage your agile project, helping you fail quickly and spectacularly.
|
|
|
Agile Model-Driven Development Despite what you might have heard, modeling is an important part of agile software development. Find out how agile model-driven development fits into the overall agile development lifecycle in a lean and streamlined manner and can improve productivity on your team.
|
|
|
Let's Talk Agile Agile development employs more oral communication, feedback, and interaction than traditional development. These communication tools can help ease the transition into the more interactive agile team relationship.
|
|