Related Content
 |
Why Do IT Professionals Succumb to Project Overload? Joe Townsend explores why IT professionals continue to succumb to project overload. The problem is not that we take on too much; the problem lies in the fact that we don’t manage our projects very well, and these repeated failures lead to overload as we can’t deliver what we promise. |
|
 |
Five Reasons Why Agile Can Fail Unfortunately, some projects fail, even when using an agile development methodology. Instead of just rehashing horror stories, Joe Townsend attempts to get to the bottom of why these failures occur. |
|
 |
Why You Need Accountability in a Scrum Development Team Often a developer who questions his team members and follows up with open-action items will be regarded as being rude. However, sometimes you need people to hold others accountable for their actions if you want your team to be successful. |
|
 |
When Smart People Do Dumb Things Smart people obviously do a lot of smart things or they wouldn’t be considered smart people. But smart people sometimes do dumb things too. Naomi Karten gives us the rundown on what causes otherwise intelligent people to behave in foolish ways. |
|
 |
The Difference between Outcome and Output in Product Development To be successful in product development, we must minimize the number of product features while also delivering what the customer will like. In other words, product development success is governed by our ability to maximize the “outcome” rather than “output” of product development. |
|
 |
The Myths and Realities of Creativity Are you creative? Most people, if asked, say they’re not—but they’re wrong. One of the most common myths about creativity is that only artists, writers, and musicians are creative. Another myth is that creativity depends entirely on the person and not on the person’s environment. |
|
 |
Signs of a Doomed Project Naomi Karten shares some common signs of a doomed project. The early signs of a project in trouble include a lack of interest, chronically poor communications, a no-bad-news environment, and people attending meetings but not paying attention. |
|
 |
Why Retrospectives Are Important in Agile Software Development Periodically reviewing how things went—and looking for ways to improve—is an essential part of agile software development. Retrospectives are one way to do this, but it’s important to understand that there is a difference between a structured retrospective and “just talking about what happened.” |
