Select Page


Top 10 Project Initiation Questions – People Change Management

Top 10 Project Initiation Questions – People Change Management
By Gail Severini

Are you launching a transformational project that demands cross-functional participation or adoption for success?

If your organization’s track record at such projects is less than stellar, or this is bigger than any other similar project the organization has undertaken, then you might want to consider how to improve engagement and commitment – traction.

People Change Management (PCM) describes the discipline of helping people change how they think about their work (in this application) and how they deliver. It encompasses culture (at the macro level) as well as models, processes and tools (at the tactical level) for improving the evolution.

How do you know if your organization is ready to benefit from these best practices? These questions are directional and are intended to undercover expectations and readiness:

  1. How risky is the project(s)? How complex?
    • Has the organization attempted this, or similar projects, before?
Read the Complete Article

Project Design Phase

Project Design Phase (#28 in the Hut Project Management Handbook)
By Wouter Baars

With the list of requirements that was developed in the definition phase, the project team is able to make choices concerning the ultimate appearance of the software.

A design document is the result of the design phase in IT projects. The design document contains an elaboration of the concept and a broad outline of a technical design. The goal is to investigate what the software will look like, both technically and functionally.

In this regard, it is helpful to work with dummies in the design phase. A dummy is a quickly assembled, non-operational (or only partially operational) piece of software that serves primarily to evaluate the design. These dummies are presented to the clients, customers (or both), as well as the end users. One advantage of dummies over schemas on paper is that they resemble the finished product. Read the Complete Article

Project Initiation Phase

Project Initiation Phase (#26 in the Hut Project Management Handbook)
By Wouter Baars

The initiation phase begins with an idea for a project. No budget is yet available for the project. The goal of this phase is to write a project plan according to which internal or external financing can be requested.

Activities in the initiation phase

  • Elaborate the concept.
  • Examine the base of support.
  • Contact possible partners.
  • Investigate funding opportunities.
  • Prepare an initial global estimate of the control factors for the project.
  • Prepare a concrete estimate of the control factors for the definition phase.
  • Establish project boundaries.
  • Prepare a project plan.
  • Apply for funding or establishing contract agreements with possible customers.

Output of the initiation phase:

  • Approved and funded project plan
  • (Possible) contract with customer Operations/Decisions:
  • (Prospective) project leader
  • Client
  • (Possible) customer

If possible, installment financing is preferable to lump sum financing following the initiation phase. For installment financing, a relatively small amount of funding for the operations of the definition and design phases is requested during the initiation phase. Read the Complete Article

Starting A Project

Starting A Project (#3 in the Hut Introduction to Project Management)
By JISC infoNet

There may be many reasons for initiating a project such as developing a new information system, changing an existing system or changing a business process. For example, in a college or university some common reasons for initiating a project might be:

  • A new strategic direction for the college or university
  • A new requirement for information from a statutory body
  • New internal management information requirements
  • Introduction of a new learning environment
  • New processes for student or other administration
  • Need to replace an ageing system
  • A major software upgrade

It is a fact that systems projects are generally relatively costly, time-consuming and disruptive. It is therefore to be hoped that, whatever the reason for considering a project, the senior management team of the institution will consider the project in terms of its place in an overall strategy.

In an ideal world a senior manager (soon to become your Project Sponsor) would present you with a Project Brief that outlined what they had in mind for the project and how it fitted in with the institution’s strategies and plans. Read the Complete Article

Recommended PM App

Recommended PM App