Project Management

Having been involved with the systems methodologies field for over 30 years I have been occasionally asked what percentage of time in a project should typically be devoted to a specific phase of work, for example a Phase 1 Feasibility Study, Phase 2 Systems Design, etc. Basically, the reason the person wants to know this is to use it as a means for estimating the remainder of the project. For example, if I were to say Phase 1 represents 10% of the overall project, they would simply multiply the amount of time spent in Phase 1 by ten. This is an unreliable approach for estimating which is why I usually balk at giving out such figures.

Requirements Risk management could be a useful approach to requirements analysis, and lead to better requirements management.

High level the idea goes like this:

Risk management is an important part of project management
Requirements management is also a critical part of the puzzle
Should we be running a requirements risk management process on our projects?
The purpose of this article is to introduce the topic of Requirements risk into the Requirements Management discussion. Feedback and commentary is welcome and can be provided at ModernAnalyst.com

Whether you call them Systems Analysts, Business Analysts, Systems Engineers, or Enterprise Architects, it is very encouraging to see this vital function being reintroduced to companies. As far as I am concerned, it was inevitable. I guess companies finally figured out you cannot satisfy your systems problems simply by using better programming tools and techniques.

The project scope is the core of an individual project. Without a project scope the project will just float. Proper needs assessments and other intricate details will be overlooked. Each project is designed to resolve issues the stakeholders are experiencing in their company. These well meaning individuals will dump data and information charts, lists and figures presumptuously on the desk expecting it to all make sense. The "here's the problem, fix it" attitude can be frustrating. There are numerous feature requirements which must be met. It is unclear as to what to prioritize where. Cost estimates may not be accurate. Delivery dates are tentative. It is enough to make someone through up their hands in desperation and say "I QUIT!". The trained business analyst will just grin and dive in. He or she will know what is needed is a project scope.

Author: Tony de Bree

It does not matter what project you are going to undertake. It is not important what industry you are going to be assessing. What is important is you know what you are going to do. You must as questions. You must find what it is the client wants. Presented is a list of obvious questions every good business analyst should know the answer to when starting a project.

Author: Tony de Bree