pm
In the agile community there is a movement called “no estimates”—where people are challenging the value and validity of estimating the work required to develop software. Scott Sehlhorst looks at the different perspectives of those who challenge estimation.
When the government suddenly passes regulations that impact the development of a product, an organization's investments could suddenly turn to waste. Venkatesh Krishnamurthy explains how to deal with the waste as well as some methods to better handle inventories.
Working with vendors can pose challenges to an agile team, especially when it comes to contracting practices. How do you deal with contract relationships when trying to follow a philosophy that values collaboration over negotiation? Kent McDonald gives some suggestions for creating agile contracts.
Are projects ever completed ahead of schedule? It turns out the answer is yes, and interestingly, just as with projects that fall behind, issues can arise with projects completed ahead of schedule. Naomi Karten writes about some of these problems and what to do if you finish a project early.
Agile approaches have changed the conversation about measuring project success, from comparing against cost, time, and scope projections to looking at how much value the project is going to deliver. The problem that remains, however, is determining what value really is and how to measure it.
Joe Townsend examines why software professionals continue to fail at requirements management (RM). Some of the ways to address RM issues include using the right RM tools, proper requirements prioritization, and requirements churn.
If your project has ever slipped, you are most certainly not alone. Naomi Karten lists the reasons that lead to a broken project or one that has fallen behind, and describes what you can do to avoid catastrophe.
When planning for feature prioritization, it’s crucial for you to take into account product economics. Sameh Zeid writes that product economics helps us to understand if it is financially viable to develop a product, even more so than relying on business value.
Managers and project managers are often obsessed with measuring the time it takes to do a task. Time is useful to consider, but measuring time doesn’t always give us the information we really want or need. It's true that work takes time, but it's more valuable to measure results and value delivered.
As agile adoption continues to gain popularity, it appears that Scrum is at the forefront of many agile implementations. Given the rise of Scrum, it makes sense that you might wonder how agile will continue to evolve as new methodologies—some of which may replace Scrum—are being developed.