4 Re center project planning around business outcomes to estimate and track

4 re center project planning around business outcomes

This preview shows page 16 - 24 out of 35 pages.

4. Re-center project planning around business outcomes to estimate and track benefits. 5. Over-manage stakeholder involvement at Concept Definition.
Image of page 16
17 The problem-category pie by the five factors 14% People 8% Method 54% Project Mgt. 3% Technical 21% Business Sample contains a total of 99 observations from 17 detailed sources
Image of page 17
18 List of top seven reasons why IT projects fail 1. Poor project planning and direction 2. Insufficient communication 3. Lack of change, risk, financial, and performance management 4. Failure to align with constituents and stakeholders 5. Ineffective involvement of executive management 6. Lack of skilled team members in the areas of soft skills, ability to adapt, and experience 7. Poor or missing methodology and tools
Image of page 18
19 1. Poor project planning and direction Evidence head2right “poor planning” and “lack of empirical data” head2right “team does not have clear goals and responsibilities” head2right “missed important items that should have been caught” head2right “poor general management skills” head2right “does not assign the right people to the right task” Recommendations head2right Utilize a planning method * supported by a tool Remember the 4 Ps and don’t Plunge head2right Make clear assignment to team members and make changes as necessary *Rules, processes, and tools for project planning and project management.
Image of page 19
20 What is a planning method? Organic method (items that appear in internal company guidance) 1. Set up an electronic project notebook (repository) 2. Establish written project objectives (communication) 3. Work with the technical lead to establish tasks within phases (planning) 4. Ask team members to estimate tasks (estimating) 5. Create a formal project plan and manage to it (directing) 6. Proactively solve problems that arise (problem solving)
Image of page 20
21 2. Insufficient communication Evidence head2right “infrequent open communication” head2right “status reports are not objective” head2right “poor communication with sponsors and business users” head2right “failure to properly involve others like hardware vendor” head2right “does not broker consensus among stakeholders” Recommendations head2right Agendas, minutes, information-push emails, and for-purpose meetings or conference calls head2right Mix up the way that the message is delivered, especially for executive reviews
Image of page 21
22 How can we support the suspend and resume behavior typical of life in IT today? Senior people are likely doing several projects or supporting multiple programs at the same time Specialized personnel have a narrow focus and are often shared resources Daily professional life isn’t naturally an ordered set of activities Meetings Activities Phone calls Instant messages Emails Education Text messages Problem Conference calls
Image of page 22
23 Don’t underestimate the power of the project manager to create order Project managers can have a significant impact on creating order Order makes it possible for people to suspend and resume their activities Meetings Agenda Minutes Action items Activities Repositories Local Network Work products Tools Assist humans Automation Action items Activities
Image of page 23
Image of page 24

You've reached the end of your free preview.

Want to read all 35 pages?

  • Left Quote Icon

    Student Picture

  • Left Quote Icon

    Student Picture

  • Left Quote Icon

    Student Picture

Stuck? We have tutors online 24/7 who can help you get unstuck.
A+ icon
Ask Expert Tutors You can ask You can ask You can ask (will expire )
Answers in as fast as 15 minutes