Business rules, Process rules, Process, Data, different viewpoints on requirements.

To fully understand requirements it is necessary to break them down and consider each on it’s own merit. First of all requirements come from different viewpoints and these angles must be fully considered.
The key viewpoints to consider are: Business rules, Processes, Process rules, Data rules and models, Operating environment internal and external, Culture, Skills, Adaptability.

Communication for project managers

Before you even consider communication with any audience from one person to 100 million people, you need to first gain their respect and trust. If you don’t, why should they listen to you.
Just like you they are bombarded with messages all day every day and they only have time to listen to a choice few that come from trusted sources , that gain their attention and arouse their interest.

When is a business case not a business case (part 4)

There a re a few fundamental rules to bear in mind when presenting any proposition:

1. Recognise and understand your audience so that you can directly target a known need or desire with your proposition.

2. Use the appropriate language and context to present your proposition.

3. Get your timing right.

4. Demonstrate understanding of and sensitivity to the operating environment.

When is a business case not a business case?

You can talk to five different people who have that word in their CV and each one will probably have a different take on what a business case is for, who should prepare it and what it should contain.
In fact, you could say that the whole science around business cases, especially those involving IT investment has moved on substantially in the past two or three years.

When is a business case not a business case (part two)

A key to building a rock solid business case is to understand the relationships between requirements, features, benefits and risks and to take a methodical approach to evaluating likely ROI as a key part of the process.

Selecting Waterfall, structured, Iterative or agile for your software project

First lets understand the difference. Waterfall is the most misquoted of all methods. Waterfall is defined by the simple fact that each stage in the project must complete fully and be agreed/signed-off before the next stage can begin. Sometimes it is very important that the previous stage was fully and correctly completed. An example would … Read more

About the author

Edward Taaffe has a 10 year record of achievement in project and Programme management in both the private and public sectors ranging from negotiating with local authorities to use centralised shared services to introducing ground breaking technology to government and convincing them of the benefits of early adoption. Previously and interspersed with this, he has … Read more

The true DNA of an agile project (exploding the myths)

If you have heard me pour scorn over some of the claims made for agile, you may be surprised to know that I’m an agile practitioner with some considerable experience and not at all adverse to the approach. That said, I always repeat the words of my agile mentor Keith Richards (no not him silly) when I asked the obvious silly question. He said ” It’s horses for courses. When you turn up for training we assume a certain level of education, intelligence and experience”.