Slide 133 of 262
This is a snippet from a Project Plan in project software. I am a firm believer in project plans. Even smaller companies should use a plan. I am also aware of how often they change with circumstances.
I highly recommend a tracking method. One of the worst things you can do in an implementation is lose control of the status of the project on a level of individual responsibilities. At Motorola in Guadalajara we help meetings every Thursday. It was in the ‘War Room’. Chairs were removed from the conference room. Each element had been assigned to a point person. Systems documents and status were posted on the walls as well as an overall progress chart. Every ‘point person’ had 5 minutes to state the status of their element and 5 minutes more to answer questions. The plant manager and all upper management attended each meeting. Absences were simply not allowed and there were none.
This forced communication and an honest assessment weekly (we did the implementation in 6 months - ~4000 souls). If someone had a resource issue, this meeting is where it was to be brought up for immediate resolution (no waiting while upper management ‘thinks about it’).
See slide titled: ‘Typical’ Detailed Implementation Steps Example
Example Project Plan Snippet