PROJECT MANAGEMENT

Project management

Project Management

Question 1

Stakeholder identification and management is a key skill for all project managers, program managers and executives (collectively called project manager for the purpose of this paper). Stakeholders are individuals who represent specific interest groups served by the outcomes and performance of a project or program.

Identify Stakeholder

Inputs

Tools

Outputs

Project charter

Procurement documents

Enterprise process assets

Organizational process assets

Stakeholder analysis

Export judgment

Stakeholder register

Stakeholder management strategy

Stakeholders for this project includes e:

Community groups

Industry or business associations

Environmental groups

Local councils

Government departments

Communication is - in my opinion - the number one skill that a project manager needs to have. Going into any engagement who the project manager will be communicating with is a question mark because the project itself can be more far reaching than originally imagined.

Now those finely honed communication skills are going to come in handy. In order to determine the specific goals of the project, there is a need to meet with each of the key stakeholders and document their ideas of this project goals. It's also a good idea at this point to gain an understanding of their needs and concerns regarding this project. Perhaps the existing business processes, and the systems that support them, are so old that little documentation exists for them.

Question 2

To advertise and recruit required professionals.

To analyze and document the specifications for the required functionality.

To acquire the needed hardware and software as part of IT infrastructure facilities.

To design, implement, test and operate the entire system.

Next step is defining human resources in terms of category, seniority and hourly cost:

Functional expert(s) - Knows the business process

Technical support - Technical product knowledge

Workflow Business Analyst - Workflow tools expert

System Administrator- Maintain workflow environment

Business Analyst - assist in doing a business process analysis

These days, the cost of the project is often fixed before the design is done, and sometimes even before design has begun. Estimation now becomes more of guesswork based upon experience that was gained by screwing up earlier estimates. Without the design, it was quite impossible to know how many lines of code/functions/components/objects would be required. The estimator should rely on data and documents available before one starts the design, such as the functional and non-functional requirements, workflows, and use-cases. Therefore, requirements gathering and analysis is very critical to the project's estimation (design, development, and testing).

Using these documents, the estimator may create an object hierarchy tree simultaneously. The object hierarchy tree can help identify different levels/types of objects to be created, what is expected from these objects, and even some attributes for the objects. Therefore, without having an application design in place, the scope of work to be done, in terms of functionality required, can be identified.

You need several types of inputs for the company to create a project schedule:

Personal and project calendars - Understanding working days, shifts, and resource availability is critical to completing a project schedule.

Description of project scope - From this, you can determine key start and end dates, major assumptions behind the plan, and key constraints and ...