• Agile September 2015 training blog ad-02

project management

Homer Simpson, Difficult Stakeholder

I am a firm believer that any situation in life or in business can be traced to an episode of either The Simpsons or Seinfeld. In The Simpsons season 2 episode “Oh Brother, Where Art Thou,” the patriarch of the Simpson family designs a car, which provides a surprisingly sophisticated …

Read More

“A Poor Craftsman blames the (requirements) tool”

The decision to use a requirements tool is dependent on a number of factors: size of project, number of system interlocks, global teams, specific business objectives tied to real dollar figures, just to name a few.  In this post I will describe the key benefits of using a requirements management …

Read More

Using Revenue Properly to Measure Project Success

Objective measures are needed to determine the success and failure of commercial software development efforts. The feedback for companies that sell software as a product or as service is immediate and determined by the marketplace – they either have revenue or they do not. However, for software developed to use …

Read More

Requirements Tools: Excel (1 of Many)

Last time, I went over a Sharepoint feature that’s saved me a lot of time and effort. At Seilevel,, as much as we use Sharepoint, we use Excel even more. Not as much for calculations, but for storing and sorting requirements and associated data, such as features. When we do …

Read More

Using visual models to prioritize features

One of the most difficult tasks on any project is prioritizing requirements. This is because there is almost always disagreement about what the priorities should be.  The more stakeholders you have, the more disagreements you’re likely to have.  It is human nature to avoid conflict and that is why many …

Read More