Related Content
 |
Removing Waste in Software Projects 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. |
|
 |
Create a Vendor Contract While Keeping Agile 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. |
|
 |
Making Assumptions on Projects Is a Ticking Time Bomb Assumptions are a fact of life. Without making assumptions, it’s unlikely that many decisions would get made, and certainly fewer projects would ever get launched. However, sometimes assumptions come back to haunt us. Adrian Reed looks at how to handle assumptions when working on projects. |
|
 |
Creating Software from a List of Things? Then Don't Call It Agile There are two ways to think about scope—a list of things to be done or a list of goals to accomplish. As long as scope is defined as a list of things, then your project process is not agile, even if your team is using the mechanisms of agile development within the code creation cycle. |
|
 |
What Happens When Projects Are Completed Ahead of Schedule? 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. |
|
 |
Why Being Simple Is Better Than Being Simplistic Product managers know that a product needs to be simple to succeed in a market. Although being simple is a product virtue, being simplistic can be a product vice. Scott Sehlhorst evaluates why it's better to create a product that is simple—not simplistic. |
|
 |
Tips for Managing Conflict You can’t avoid conflict at work. Once differences surface, a catalyst for serious conflict is the tendency for the parties to treat their differences as a zero sum game: For one party to win, the other has to lose. It doesn't have to be that way. Naomi Karten gives some tips for managing conflict. |
|
 |
Why a Product Strategy Is Not a Product Plan Strategy is important not just because you want to be intentional but also because strategy makes you more efficient. Strategic activities ensure the intended product is the right product. Scott Sehlhorst looks at why a strategy is not a plan; instead, strategy guides planning. |
