Project – Definition
For IS projects, the definition needs to expand to identify if the project will be only software based or will hardware be involved. Sometimes at this point, it is not known if new/updated hardware is needed but the project charter needs to identify as much as possible. The definition of the project helps to identify stakeholders that are impacted by the project. Knowing who the stakeholders are will help to define what the expectations of the project will be. “It is vital to integrate key stakeholders’ needs and thereby to gain their trust and support” (Susniene’, 2007, p.24).
In today’s corporate environment, a lot of IS projects will involve external stakeholders because of the need for specialized resources to help with the software and/or hardware implementation. Identifying in the project charter the need for external resources to work on the project will be important. It will help to determine if these external resources should be listed as stakeholders.
Kendrick (2004, Kindle Location 1005-1009) outlines what most project charters should include:
> Project objective statement
> Project priorities
> High-level scope statement, describing all expected deliverables
> Description of the expected users or customers
> The business case for the project (benefit or return on investment analysis)
> Rough cost estimates
> Target milestones and deadlines
> Project leader and initial staffing information
> Identified dependencies
> Key constraints and assumptions
> Known issues and high-level risks