Now the different team structures and team building phases have been discussed we will now zoom in on the execution phase. The project experiences will be shared of the primary interpersonal issues, the impact on the team relationships till taks accomplishment and project management action strategies. This will give first-hand …

During my career all kinds of teams has been working on the projects. The team size depends, and also the team structures. Let us discuss the different team structures and how to going through the team building phases. The team building phases are clearly written out by Donald Egolf in his Forming, Storming, Norming, Performing: …

We all know what communication is: a two-way process in which we act as transmitters of information to someone else, the receiver. The objective, of course, is to generate some response in the receiver. The desired response is usually to get the receiver to take some form of action. If the process of …

Revisiting Requirements Elicitation. Requirements elicitation is the process of discovering and clarifying the needs, capabilities, conditions, and constraints that a project must satisfy to deliver a solution or product that meets the client/market needs. Requirements elicitation is by far the significant activity taken by a business analyst or requirements engineer. …

How to use traceability and what’s the value of traceability? In this part, let’s look at what traceability can be used for and where it delivers value to application, system or product development. Why is traceability necessary/important? Isn’t traceability just an overhead, an onerous documentation task that’s only done in …

What is traceability? Or more specifically what is requirements traceability? Well rather than repeat what is already a good collection of definitions, I’ll refer you to http://en.wikipedia.org/wiki/Requirements_traceability. From there I’d summarize three elements to requirements traceability: Following the life of a requirement – from idea to implementation How requirements impact each …

Why base line your requirements? Usually projects start with unclear requirements and expectations. Lack of base lined requirements can result in chaos with lots of requirements changes resulting in requirements and scope creeps. Baselines can also help in acceptance testing and prototyping efforts. Baselines are especially valuable in fixed price …

How to write good requirements and types of requirements? Requirements are the starting point for everything – project scoping, cost estimation, scheduling, coding, testing, and release management. If the requirements captured doesn’t serve the purpose that are supposed to do; there is hardly any benefit in spending time and money …

What is requirements management and why is it important? The world of requirements management has developed significantly in the last decade or so and has increasingly become one of the corner stones of successful software and systems engineering projects. We have been discussing various aspects of the domain from a best …

This “Seven  Step Planning” is written in an interactive style and targeted for non project managers and entry-level project managers on “How to Plan an Undertaking/Initiative or a Mission/Project”. It’s received during one of the many project management courses and was very useful for me to apply in the field. Step …