‘Collect Requirements’ is an important process for the success of a project. If stakeholders requirements are not collected adequately that leads to a scope which is poorly defined. If the scope is wanting then the deliverables are not well defined and if that is so then project creates deliverables that do not match customer expectations. In such a scenario even…
Methodology is not a silver bullet that can fix projects by itself. But it does help in giving a clear roadmap for achieving project success.
c to look for unexpected impacts of implemented risk responses.
Identify stakeholders as early as possible, create their management strategy and manage their expectations throughout the project life cycle.
WBS is a good tool for communications and team buy in.
Projects are ‘strategy enablers’. They should be professionally handled to achieve required strategic results.
If a scope has to be curtailed then first look to get rid of requirements with higher costs and lesser benefits
Think of WBS dictionary as work package dictionary which defines the overall scope of the work package.
Remember when using Schedule compression techniques, ‘Crashing’ often results in increased cost while ‘Fast Tracking’ often results in increased risks.
Do perform schedule compression during ‘Develop Schedule’ process but don’t forget to update ARR(Activity Resource Requirements)