Effective IT Project Management: Using Teams to Get Projects Completed on Time and Under Budget

IT Phase 4 ”QA

  1. Fixes bugs

  2. Reviews Documentation s documents

  3. Works on Help Desk s QA testing

  4. Develops and presents TOI

  5. Attends phase review

Communications Phase 4 ”QA

  1. Joins project team (this may begin in Phase 3 depending on length of QA)

  2. Works with Business Development to create Announcement Plan:

    • Works with PR firm to identify press and analyst themes

    • Updates corporate positioning

    • Works with design firm to develop project identification look

    • Develops press kit

    • Decides on user positioning for case studies

    • Works with PR to identify press and analyst lists

    • Works with PR to develop press tour

    • Works with advertising agency to decide advertising plan

  3. Attends phase review

Business Development Phase 4 ”QA

  1. Business Review Document and financial analysis are updated

  2. Announcement Plan is created:

    • Message and market positioning are decided:

    • Announcement date and strategy are decided

    • Core project write-up are developed

    • Project presentation is developed

    • Pricing analysis is developed

  3. Potential beta users are contacted

  4. Beta sites are presented to project team

  5. Early sites are briefed

  6. Sales channel training is developed

  7. Project numbering and ordering information are developed and coordinated with finance

  8. Works with order entry and manufacturing to create a Release Plan

  9. Attends phase review

Project Manager Phase 4 ”QA

  1. Confirms that Business Development updates market review and financial analysis

  2. Confirms that beta sites are solicited

  3. Facilitates information flow between QA, Documentation, and IT

  4. Confirms that severity 1 and 2 bugs are fixed

  5. Manages TOI

  6. Creates the Release Plan

  7. Presents Market Plan, a highlighted list of the expected launch deliverables, Beta Plan, and project status to executive staff (Phase 4 review)

QA Phase 4 ”QA

  1. Begins full testing

  2. Uses documents when testing project, gives recommendations to Documentation

  3. Creates bug reports , confirms bugs are fixed

  4. Provides team with approval to move to Beta

  5. Attends phase review

Help Desk Phase 4 ”QA

  1. Finalizes project Help Desk Plan

  2. Confirms Help Desk organization is prepared to support the project

  3. Provides Project Manager with training list for TOI

  4. Identifies user training classes that will be needed

  5. Works with QA to identify beta user escalation path

  6. Attends phase review

Documentation Phase 4 ”QA

  1. Receives team s input, updates documents

  2. Presents second draft documents to team

  3. Receives team s input, updates documents

  4. Attends phase review

4.9 in a Nutshell

Each team member is responsible for executing a number of tasks .

Related

Категории