Related Content
 |
The Truth behind Software Development Estimates The problem with estimation is that software is not construction. We can’t create software the same way we build a house or manufacture anything else. We can't say, “We can build this software for x dollars per square foot.” But other people often think of our estimates that way. What can you do? |
|
 |
How to Hold a Productive Project Status Meeting Status meetings let team members report what they’re doing and whether they’re hitting targets, and they help the project manager identify weaknesses early and make adjustments. Unfortunately, all too often these meetings are boring. They don't have to be! Read on for tips on making them productive. |
|
 |
What Is the Difference between an Agile Coach and a ScrumMaster? Joe Townsend explores what exactly the role of an agile coach is and how it differs from the role of a ScrumMaster. For some, ScrumMasters are the front-line fighters and agile coaches are higher up in the organization; for others, an agile coach is the next role a ScrumMaster evolves into. |
|
 |
Adopting Agile Means Accepting Change: What to Do? Adopting agile means change. And change is hard. But if your current process isn't working as well as you would like, you may need to change. The challenge is to explain the value of agile in a way that helps people open up to new ideas. |
|
 |
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. |
|
 |
How to Present Your Ideas So They Have the Best Chance of Being Sold Have you ever proposed an important change and those in charge stubbornly refused to back your ideas? Consider whether it was because your proposal was one-sided, misdirected, or poorly packaged. To persuade managers, stakeholders, or customers to support your ideas, keep these points in mind. |
