Many of us work on projects, as team members, line managers, users, support groups or project managers. Most of these projects are cross-functional and/or cross-business, in that they span multiple departments, groups and borders within an organization.
One of the top reasons projects fail, is that they do not deliver the product, service or result that the customer actually needed, as opposed to what they said they needed or thought they needed! Even if the project finishes on time, on budget, on specification, is it considered a success if it did not produce the value actually needed by the customer? Worse yet, questions are frequently asked about the project's origin, mission, business objectives or, in fact, “should there even have been a project?"
This workshop covers basic, fundamental things the project manager and their team need to know to avoid these major pitfalls, whether they are working on a project with a lesser or greater degree of overall uncertainty. It teaches participants how to work with the customer to derive “what is actually needed", in projects with varying degrees of uncertainty. Traditional methodologies are presented and practiced, for those projects with relatively little uncertainty (predictive/“waterfall" projects). Agile methodologies are presented for projects with a greater degree of uncertainty (adaptive projects). Increasingly, organizations and project teams tend to adopt hybrid methodologies to manage projects, by tailoring their approach to the specifics of the organization, the environment, the product, etc. View learning objectives.
Whatever methodology is practiced, the goal remains the same: build the right thing, the first time!