Related Content
 |
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. |
|
 |
Companies Going from Public to Private—Is This a New Trend? In the lifecycle of a company an IPO is a significant milestone to generate the required funds to empower its operations. The mandates that follow from going public can make a company lose its long-term vision. Rajini Padmanaban profiles companies who are going from public to private. |
|
 |
Google's Organization-Wide Innovation Strategies Organizations that adopt a well thought-out strategy toward innovation and are able to allocate the required resources for it set themselves up to emerge as market leaders in the long run—both tactically and strategically. Rajini Padmanaban profiles Google's organization-wide innovation strategies. |
|
 |
Embrace Changing Requirements or Work Hard to Reduce Uncertainty? Agile development teams and practitioners can welcome changing requirements all they want—but how hard should they work to reduce the uncertainty that accompanies changing requirements? Experts have mixed opinions on the topic, and each side makes a pretty convincing argument. |
|
 |
How Agile Can Deliver on a Fixed-Budget (Not Fixed-Price) Promise Development projects run into problems any time they attempt to stick to a fixed-price, fixed-scope, and fixed-completion contract. Learn why this fixed iron-triangle sets projects up for failure and what agile teams can do to solve the problem and make the customer and the developers happy. |
