Is it more important to build the right software or more important to build the software right? The lazy answer is something like "They’re equally important." Let's not be lazy. Let's think about this...
TOOLS TRAINING LIVE WEBINARS USER-GENERATED
|Books Events Links White Papers Wikis|
|Language:||All English Arabic French Japanese Korean Portuguese Romanian Russian Spanish|
|Access:||All Free Premium|
|All A B C D E F G H I J K L M N O P Q R S T U V W X Y Z|
234 items found
We need to change the way we talk about change management. New technologies, practices, and commercial pressures have made traditional change management approaches difficult to apply effectively. Traditionalists view these new ways of working as irresponsible, inapplicable in an enterprise environment. Others have decided that change management is obsolete in a world where organizations need to be highly responsive to commercial realities. Both of these are wrong.
So you are considering getting started with Kanban, but where do you start? In this article, we describe the approach used in Danske Bank to get teams off to a good start with Kanban.
More and more companies are turning to Agile to improve their project success rates, and Scrum is the most popular method. Yet it's a challenge to find candidates with a legitimate Scrum background. How do you find people who are going to move your company forward?
Spectacular technology failures require dramatic rethinking of approaches--even in the U.S. Federal Government.
To thrive in this new age of hyper-change and growing uncertainty, it is now an imperative to learn a new competency—how to accurately anticipate the future.
It’s hard to find a use case that is tougher than bringing DevOps tools, processes and culture to bear on a company that centers around building physical devices--large and small. But that's precisely the journey Alan Schachtely, director of software engineering at GE Software, described in a recent presentation.
Need a concrete example of how to get started with acceptance-test driven development on an existing code base? It is part of the solution to technical debt.
Visual specifications are a powerful way of increasing our understanding of requirements and increasingly help us determine if our intended solution will solve the problem and be usable.
Are Use Cases, the long-form way to document functional requirements, now dying or even dead? Has Agile killed them?