by Mark Davison
February 3. 2011 13:24
Action #
Group
Sub Group
Status
Description
Comments/Update
Date Logged
Logged By
Date Assigned
Assigned To
Target Date
Follow Up/Closing Comments
Date Completed
by Mark Davison
February 3. 2011 13:22
1.0
Product Overview/Goals/Objectives
1.1
Project Summary
1.2
Assumptions
2.0
Contact List (Business, IT)
3.0
Customer / Business Units Impacted
4.0
Escalation Chain and Process Flow
4.1
Technical Escalation
4.1.1
Support Contact Escalation
4.1.2
Technical Management Escalation
4.1.3 Business Management Escalation
5.0
Summary of Installation
6.0
Installation / Validation Schedule
7.0
Risks and Backout Plan
7.1
Problem Reporting
7.1.1
Network Issues
8.0
Checkpoint Schedule
9.0
Issue Tracking
by Mark Davison
February 2. 2011 19:52
- Accept that some of ERP implementation is art, and some is science, and manage both
- Email is a great tool for communication but not a substitute for face-to-face and phone conversations that are often more effective
- Make sure the project team, end uses, stakeholders, and others are engaged to ensure buy-in and forward movement
- Do what it takes to keep enthusiasm and interest - it can be a long road - we've seen everything from picnics and parties, to redecorating the office, providing music and snacks, to contests and marching bands!
- Ask for status and updates from everybody, frequently and in a curious way, to find out what's happening
- You're the PM - be the leader, spread the vision, embrace and promote the plan, come with an agenda, think ahead, encourage, support, guide, direct, set the example, make sure people get it, and lead the way forward
- Think about the relationships you'll need to succeed, build them early so that when you need to ask for help the foundation is there
- When it comes to a choice between technology and process don't forget that processes leads, technology is supposed to provide the tools
- The corollary is that sometimes it's great to apply technology and sophisticated solutions, but functional, technical, time and money requirements might be better satisfied by low-tech, quick-and-dirty solutions that can be just as good
- Recognize accomplishments - both big and small
- Thank others for their work and commitment
by Mark Davison
February 2. 2011 19:28
10. Has the operating system been updated?
9. I can't test everything!
8. THIS program can't do THAT
7. I haven't touched that module
6. Didn't I fix that yesterday?
5. It worked yesterday
4. The test data is wrong
3. It must the wrong executable
2. Somebody must have changed my code
1. It must be user error!
by Mark Davison
February 2. 2011 15:37
- Understand it. Learn the reasons why change is taking place, and change what you're doing to contribute.
- Think about what you can control. Don't let the stress obscure your view of what you can control, and what you can't - then focus on what you can.
- Remember the consequences - they may not be pretty.
by Mark Davison
February 2. 2011 14:59
Risk of taking action
Risk of not taking action
Benefits may not become reality
Costs of the project or technology are underestimated
Resources (internal, external) cannot perform
Technology cannot perform
Processes immature/cannot meet requirements
Security inadequate
Backup difficult/expensive
Insufficient utilities (electric, gas, etc.)
Privacy issues
Possible business downturn
Insufficient capital/funding
Lack clear definition of roles/responsibilities/decision making authority
Lack standards
by Mark Davison
February 2. 2011 14:55
Existing people, processes, technologies, equipment and facilities
Resistance to change (culture)
Lack of technology and process integration
Lack of meaningful measurements
Limited work space
Lack of previous project successes
Lack of management awareness/involvement
Lack strategic focus
by Mark Davison
February 2. 2011 14:52
Important to maintain standards
Keep users involved and informed
Follow/use the methodology for SDLC and PM
Follow/use workplans to manage schedules, resources and deliverables
Select vendors carefully - not your best friend, but the best qualified
Define success criteria
Get user ownership via sign offs, walk throughs and status meetings
Use all media to facilitate communications: personal, electronic, etc.
Adapt to ongoing change
Measure what's important (what gets measured gets done)
Pause to share lessons learned, and incorporate them next time
Up front requirements defined well are essential
Have the "right" people on board to meet goals and objectives
by Mark Davison
February 2. 2011 14:48
Communicate
Coordinate
Connect
by Mark Davison
February 2. 2011 14:47
1. Do what's right
2. Do the best you can do at all times in all ways
3. Treat others like you would like to be treated
4. Have faith in yourself
5. Tell others you appreciate them
(Thanks to Lou Holtz - a tape you produced years ago inspired the application of these concepts to IT project work!)
Subscribe
Filter by APML
