Archive of Consulting Articles

Just Plain BadLameAverageGoodGreat (3 votes, average: 5 out of 5)
Loading ... Loading ...
October 9th, 2006

Goal-Driven Documentation

Why do we write documentation? Because someone told us to write it? Because our competitors have it? Or because we want our software to be easier to use? It should be the third one, but often, writing documentation is an afterthought, and it is deprioritized, and we just get it done, instead of thinking about the goals for doing it in the first place and doing it right.

Just Plain BadLameAverageGoodGreat (Be The First to Rate This Article)
Loading ... Loading ...
September 6th, 2006

Customer Service and Software Development

Sometimes we forget that people use our software. Neil Mix reminds us that we should treat our users like people. For anyone who’s worked retail or food service jobs (like yours truly), we shoud treat our customers like customers.

Just Plain BadLameAverageGoodGreat (2 votes, average: 3 out of 5)
Loading ... Loading ...
August 29th, 2006

Building the Case for Requirements Management Tools

Marcus Ting-A-Kee has assembled a great presentation on the value to his company of requirements management tools. In addition to creating the presentation and sharing it with all of us, he shares the process of creating the presentation in several articles.

Just Plain BadLameAverageGoodGreat (1 votes, average: 5 out of 5)
Loading ... Loading ...
July 19th, 2006

Communicating A Release Schedule With Use Cases

We manage release schedules with project management. We manage customer expectations with consulting skills. How do we manage customer expectations about release schedules? With Use Cases.
Background
We started a series of posts exploring why we apply use cases as part of product management, identifying 8 goals for which use cases are [...]

Just Plain BadLameAverageGoodGreat (Be The First to Rate This Article)
Loading ... Loading ...
July 17th, 2006

Communicating Intent With Implementers

Giving a functional spec to developers and testers is not sufficient for creating great software. To a developer, a spec is only the what and not the why. And for a tester, the software requirements specification is neither. Use cases provide the why that explains the intent of the system for the implementation team.

Just Plain BadLameAverageGoodGreat (Be The First to Rate This Article)
Loading ... Loading ...
July 14th, 2006

Communicating Intent With Stakeholders

We can build a prototype of what the stakeholders don’t want, and then get feedback and fix it. Or we can review use cases of what we intend to build, confirm that each stakeholder wants it, and build it right the first time.

Just Plain BadLameAverageGoodGreat (Be The First to Rate This Article)
Loading ... Loading ...
July 11th, 2006

Outside Reading: Top 10 Signs You Should Not Write Requirements

Seilevel has a post that presents the top 10 signs that you should not pursue a career writing requirements, check it out. Thanks Joy for the great article!

Just Plain BadLameAverageGoodGreat (2 votes, average: 4.5 out of 5)
Loading ... Loading ...
July 5th, 2006

Make Your Meetings 60% More Effective

While effective meetings may not be the key to success, ineffective meetings are inarguably one of the largest time wasters in corporations. Applying these tips before, during, and after meetings will make us much more effective.

Just Plain BadLameAverageGoodGreat (Be The First to Rate This Article)
Loading ... Loading ...
July 3rd, 2006

Customer Independence Day

If This Be Treason, Make the Most Of IT! (Patrick Henry)

The customer is always right, except when he is wrong. When we have bad customers, we should fire them. Declare today as Customer Independence Day, where we declare our independence from bad customers.

Just Plain BadLameAverageGoodGreat (3 votes, average: 2.67 out of 5)
Loading ... Loading ...
June 29th, 2006

Extra Features Cause $245,000 Loss

Robin Lowry has posted a story of a demo gone horribly wrong at The Product Management View. In the story, users end up confused by the myriad of features of the software - resulting in a $5,000 sale instead of a $250,000 sale.