Related Content
 |
The Cost of Delay for Not Shipping on Time The cost of delay is the way to think about the revenue you can lose plus the cost of continued development. When you delay your release and don’t ship on time, you miss the revenue from the maximum sales times. Shipping on time isn't always easy, but it's easy to see why you need to. |
|
 |
Can Innovation Be a Result of SMART Goals? Adopting innovation as a driving theme for an organization raises the important question of how best to set goals for achieving innovation. One of the popular philosophies of goal setting is better known as SMART goals, which stands for specific, measurable, attainable, relevant, and timely. |
|
 |
Does Facebook Run the Risk of Gradually Getting Cannibalized? It can be argued that Facebook is running the risk of getting cannibalized by newer competitors who are smart enough not to take Facebook head on—given its humongous size—but instead are attacking it feature by feature. Anuj Magazine examines the risk for Facebook. |
|
 |
The US Government's Configuration Management Problems Joe Townsend probes the news and finds several stories detailing the US government's problems with configuration management. According to Joe, the defense industry and government agencies should be able to improve if they follow their own standards and directives. |
|
 |
Ease Your Transition to Agile and Learn What Your Team Needs If you are starting a transition to agile, first ask yourself: Why do we want to transition to agile? Agile is about the ability to respond to change. Once you understand what your organization’s issues are and you can resolve them, you can move to a program. |
|
 |
Focus on Users' Needs Rather Than on Your Software Product Bonnie Bailey explains that you need to take care of your users’ needs first, and then, just maybe, they will explore the fabulous features of your software. When we focus on our product rather than on what the user is trying to get done, we suffer from marketing myopia. |
|
 |
Stop Blaming Changing Requirements for Your Project's Failure Blaming changing requirements for a project's downfall is about as misguided as it gets. When you start accepting that change is in coming and you start preparing for it by using iterative development, you'll see that dreading or fighting change is the only way to ensure failure. |
|
 |
Mastering the Black Art of Software Project Estimation Estimation at the start of a software development project doesn't have to be done blindly; nor does it have to involve making empty promises. By incorporating agile—or even an estimation center of excellence—both customers and developers can have a much clearer view of the road ahead. |
