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.

More projects fail because of poor change management than probably any other factor.  People do not like change and it is important to develop a change management and communication plan.  Identify that person in your group who loves to lead the charge on change.  Then develop a group discussion on how this project will impact the organization.  Draw an organizational chart on the board and circle the stakeholders.  Look at how the project will impact end users, customers, managers, executives.  How will that change be communicated to each of those groups.

Identify the leader who will begin to develop the change plan.  How will the team be structured to complete this deliverable.  A draft should be completed by the end of the week and a group will need to work on the content and strategy for that deliverable.  You can facilitate discussion in the large group and then assign a small group to work on the deliverable.  Or you can have several groups assigned to change and communication items for the plan.  Don’t hesitate to assign homework so this is completed and ready for presentation by the end of the week.

What are some of the creative ways to communicate to the organization?  Do you want to develop a web page? a newsletter, tweet program, blog, regular program for sending emails?  Will the communication look different for each group?  Let the group help stimulate this discussion and get a feel for the culture of the organization and how it communicates.  My experience in organizations demonstrates how communication differs, a small organization may communicate only by email, others may have formal presentations and still others may have comprehensive web sites.  Stimulate the group to come up with all the venues that they think will work for their organization and then assign a small group to incorporate the ideas into the plan.

One more step in the starting week of implementation/upgrade planning.

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.

Consultantshave called this week with questions regarding how to respond to RFP’s when they ask for specifics about conversion.  At a high level, the critical data elements are determined, mapped, converison scripts written, conversion run and tested.  So what would be each individual step?  Next time you run through conversion document the steps and post them as a comment for all of us.

The second question was around variable comp and formulas.  If you have any standard formulas that you may be using on an implementation, I know a consultant who would appreciate some help.

So what projects are back in play and what old standards continue.  I’ve heard DIMHRS is into testing and continues to continue.  Lot’s of organizations looking at upgrades to 9.0 but making a decision to move forward is often a slow process.

Please feel free to comment and watch as we add eBooks and other interesting information to the blog.