How will the project be administered?

Projects need to have a governance model and the project team needs to understand the model and agree to work within it’s construct.

How this activity works:
By reviewing the standards of the methodology you are using.  Will it be Compass, Rational, or some similar project methodology.  Many groups are looking to Agile to implement or upgrade faster. This might be a good methodology if your technical team is also solid in understanding the functionality associated with the application.
Reporting relationships will be identified and how status reporting will take place is important to the success of your project.  Do you have a status report template so all reporitng is consistent.

Determine status reporting responsibilities
 How often will you require status reports? Daily? Weekly by team rolled up once a month by Project Manager?  Discussed at weekly meetings?
 What is the format or template that will be used for your status report?  How can you determine at a quick glance the status of the project.
 Who should receive the status reports? How will they be distributed, posted?
• Define project filing system/repository or project diary to maintain all information in a central location.
• Determine meeting schedules and format
• Determine issue resolution procedures
• Determine change request procedures
• Determine configuration management procedures
• Determine quality review procedures
 how often
 who will perform
 what will they review

Management Procedures

Objective
To determine the tools for tracking the project and how we will measure progress and budget
Overview
How this activity works:
This discussion is about the collection of input, processing and reporting of project information and what tools will be used for these activities.  Examples such as Excel, Project, Word, Powerpoint for progress presentations (standard project template, logos etc..

It begins with the your methodology standard as a “straw man”.
Additional Materials
Distribute methodology standards

Let’s talk about some of the roles that you might want to consider for your project.  Depending on the size of the project, you may or may not need all of the roles but someone will have to assume the responsibilities.

Client Executive:  The client executive is responsible for the overall relationship with the customer.  This is the role that would address and resolve issues that cannot be resolved at the  vendor level. They keep the customer aware of new products, services, and software updates as they become available.  They are also the ones who look for opportunities where they can add value to the customer’s business.

Program Manager: The Program Manager may support the Client before and after their software acquisition, especially on large complex projects.  Sometimes called the Enterprise Manager, they would be a part of the Client’s Steering committee and should help shape the project success through the use of best practice, project and business practice.

The Enterprise Manager participates on the Steering Committee, and helps drive the project through to success.  They use industry best business process and practice.  They provide advice that will minimize risk and accelerate the implementation or upgrade.  Many organizations use the engagement manager and project manager interchangeably, however, their responsibilities re significantly different.

Project Manager: The individual in this roles provides the leadership for the project team and produces the status reports, plans, budgets and formal methodology (such as CSC, Compass, Rational) and resourcing.  The Engagement Manager supports the Project Managers both client and consulting in all aspects of project planning and control, and supports the design,development and deployment of a strong quality program.  The Project Manager is responsible for the “care and feeding” of the consulting and client project team members and for supporting the client Project Manager.

Process Specialists (Functional and Technical) Functional specialists are charged with guiding the project team through those steps that require detailed applications functional knowledge and related industry best practices. This consulting-sourced role is usually a full-time member of the project team.

The Technical Specialist executes the technical steps by providing support in the design and management of databases and in tuning the system and architecture. This is a consulting sourced role working in lock step with the client role.

System Engineer The System Engineer designs and creates technology solutions in response to business requirements. They are brought into a project when the solution requires some specific knowledge in the emerging technologies. Skills include: Workflow,  Electronic Commerce; Security including OLAP, Multi-dimensional modeling, compare report decisions, eApplications and solutions to customization requests.

Education Representative This person is responsible for working with the customer to make sure they use the education resources available to them in the most effective manner. This includes executing training plans, setting up on-site classes, and making the customer aware of alternate training formats including stand up training, interactive training, webinars and other venues. It is also the responsibility of this role to have a clear understanding of the business processes used and reflect those processes in User Productivity Kit or Tutor development.

Planning is so critical for a project and what makes a project successful is in the way you approach the first few weeks.  I have conducted these strategy and implementation workshops in a week but the work of the team goes well beyond that.  The first few weeks, however, are what can determine success or failure for a project.  So far we have discussed how important it is to get a project right the first time, the importance of scope, and organizational impact or change.  Another important factor that needs to be addressed in the first week is how you will handle issues that arise during the project and what the process will be for resolving those issues.

If you are working with a standard implementation methodology there is probably a process for issue resolution.  If not, develop a database, excel spreadsheet or similar method for tracking issues.  It is important that you establish what an acceptable time frame is for resolution and what will be done if the issues are not resolved in a timely manner.  What are the roles involved in the resolution process, who identifies, who assigns, who tracks, how high up in the organization will you have to go to find a solution, and finally who determines if an issue is closed.

Issues should be addressed on a weekly basis at meetings.  If critical you might have a process in place to identify them on your project website, or even use twitter to get information out to your team in a timely fashion.

Of course, there is a deliverable that would be associated with this part of the workshop which would be a template for tracking issues.

So we have now addressed one more small part of what would happen in Day 2 of your implementation/upgrade workshop.

Looking forward to any additions you might provide via comments.

So what should you have completed at the end of the Workshop on the first day.  A Goal of the workshop has been established and there is a solid understanding of how to implement or upgrade “right the first time”.

A template with a rough draft of some of the Charter information will be complete with time for review.  It is also important that team members understand they may have homework such as reading through draft documents and making comments or edits.

So what do you think should be included in a project charter?  I would suggest the following:

1. A mission statement for the project

2. Project Objectives and measuresments to establish when those objectives have been met.

3. A strategy for the project

4. A critical element is the Scope statement.  More projects fail from scope creep than probably any other factor.

5. An Issue Resolution methodology with initial issues identified

6. A Risk Resolution methodology with initial risks and level of risk identified.

7. The resource plan with roles, responsibilities and rules.

8. Constraints, Assumptions and a plan for next steps

9. An initial project plan at a high level which identifies critical milestones.

So at the end of the first day the team has started to develop the deliverables and resolve some of the issues that are open.  This is the time when the Project Manager should schedule a time for a presentation to the steering committee or management team.

Communication with the team and leadership is critical and the fourth day should be used for that communication with a sold presentation in place.  We have discussed the first day and what will be addressed. The timeline for the workshops may vary depending on how extensive in terms of modules and functionality the implementation or upgrade is determined to encompass.

Please make additional suggestions or comments to enhance this program.

Our team has been working diligently to complete training for EmpoHR 9.0 for the NFC. It is the NFC’s version of PeopleSoft 9.0 for Human Resources. It is a challenging project in that we so not have access to a training database which makes the development with UPK more difficult. The User Productivity Kit is a great tool though and produces nice training manuals, online training, instructor manuals and job aids. I have enjoyed learning the development side of this application and look forward to more development of training materials and programs.