It Shall Be Released

Projects that don’t deliver incremental value run the risk of growing stale, or worse, not growing at all. By maintaining a steady stream of constant, frequent, small releases, the product or solution is in a state of continual improvement, with each release better than the last.

Develop a Hypothesis Before a Solution

A development team designed a feature to improve customer experience but things got worse. It turns out they didn’t identify the real problem or the right way to fix it. What they needed was a hypothesis for what was being changed, how that change would help, and how they would test it.

The Hungry Man Parable

In agile product development, we try to work on fewer things and stick with them until we finish. Rapid priority shifts are expensive and demoralizing. But that’s not always clear on the go-to-market side, so we need stories like the Hungry Man Parable to build better understanding.

Agile & Waterfall Application Development: Meant for Each Other?

In most IT circles, the mere suggestion of marrying agile and waterfall application development models into a seamless hybrid would be scoffed at. But there is merit to the concept.

Topic Teasers Vol. 100: PMs Supervising Code

Infrastructure Improvements: Guidance on How to Be Successful

Software infrastructure such as databases and core applications must be available 24/7 to support the business. As these infrastructure elements age, you should start planning when they will be updated or replaced. Take a look into three main areas of achieving this—making decisions, design success and selecting vendors.