20
University Information Technology Ser Project Management 102 Pragmatic Guidelines for the Uninitiated Michael Mundrane IT All Staff Conference 12 March 2014

Project Management 102 Pragmatic Guidelines for the Uninitiated

  • Upload
    jania

  • View
    57

  • Download
    0

Embed Size (px)

DESCRIPTION

Project Management 102 Pragmatic Guidelines for the Uninitiated. Michael Mundrane IT All Staff Conference 12 March 2014. Status 1/21/2014 … ok. Status 2/20/2014 … hmm. Status on 4/1/2014 … huh?. Status a Bit Later … sigh. Project Management Detail. Scope Schedule Budget Requirements - PowerPoint PPT Presentation

Citation preview

Page 1: Project Management 102 Pragmatic Guidelines for the Uninitiated

University Information Technology Services

Project Management 102Pragmatic Guidelines for the Uninitiated

Michael MundraneIT All Staff Conference

12 March 2014

Page 2: Project Management 102 Pragmatic Guidelines for the Uninitiated

University Information Technology Services

Status 1/21/2014 … ok

Page 3: Project Management 102 Pragmatic Guidelines for the Uninitiated

University Information Technology Services

Status 2/20/2014 … hmm

Page 4: Project Management 102 Pragmatic Guidelines for the Uninitiated

University Information Technology Services

Status on 4/1/2014 … huh?

Page 5: Project Management 102 Pragmatic Guidelines for the Uninitiated

University Information Technology Services

Status a Bit Later … sigh

Page 6: Project Management 102 Pragmatic Guidelines for the Uninitiated

University Information Technology Services

Project Management Detail

• Scope• Schedule• Budget• Requirements• Documentation• Milestones• Risk• Stakeholders• ...

zzzzzzz

Page 7: Project Management 102 Pragmatic Guidelines for the Uninitiated

University Information Technology Services

Rethinking This

Actually … This is not that kind of talk.

Additional process is not the solution when complexity and mismatch is the problem!

There must be a more general approach.

Page 8: Project Management 102 Pragmatic Guidelines for the Uninitiated

University Information Technology Services

Classical Project Management

There are only two high level functions for project management.

1. Accurate assessment2. Effective Communication

Does that really serve our needs?What are we actually trying to manage?

Page 9: Project Management 102 Pragmatic Guidelines for the Uninitiated

University Information Technology Services

Proposed Project Elements

Practical number of elements

Useful breakdown of actual effort

• Concept• Research• Design• Planning• Staging• Execution• Review

Page 10: Project Management 102 Pragmatic Guidelines for the Uninitiated

University Information Technology Services

Concept

• Concept• Research• Design• Planning• Staging• Execution• Review

General ideaAlignmentInitial Assessment

Page 11: Project Management 102 Pragmatic Guidelines for the Uninitiated

University Information Technology Services

Research

• Concept• Research• Design• Planning• Staging• Execution• Review

NeedsWantsTradeoffsStatus of art

Page 12: Project Management 102 Pragmatic Guidelines for the Uninitiated

University Information Technology Services

Design

• Concept• Research• Design• Planning• Staging• Execution• Review

IdentifyOrganizeSimplifyResolve

Page 13: Project Management 102 Pragmatic Guidelines for the Uninitiated

University Information Technology Services

Planning

• Concept• Research• Design• Planning• Staging• Execution• Review

AssessSequenceScheduleTransition

Page 14: Project Management 102 Pragmatic Guidelines for the Uninitiated

University Information Technology Services

Staging

• Concept• Research• Design• Planning• Staging• Execution• Review

First phaseNot disruptive

Page 15: Project Management 102 Pragmatic Guidelines for the Uninitiated

University Information Technology Services

Execution

• Concept• Research• Design• Planning• Staging• Execution• Review

Second phaseDisruptive

Page 16: Project Management 102 Pragmatic Guidelines for the Uninitiated

University Information Technology Services

Review

• Concept• Research• Design• Planning• Staging• Execution• Review

Did we understand?Did we design to our understanding?Did we plan to our design?Did we implement to our Plan?Were we right?

Page 17: Project Management 102 Pragmatic Guidelines for the Uninitiated

University Information Technology Services

Should/Could/Would

Should we – good idea?

Could we – feasibility?

Would we – priority?

• Concept• Research• Design• Planning• Staging• Execution• Review

Page 18: Project Management 102 Pragmatic Guidelines for the Uninitiated

University Information Technology Services

Development/Management

Project Development

Project Management

• Concept• Research• Design• Planning• Staging• Execution• Review

Page 19: Project Management 102 Pragmatic Guidelines for the Uninitiated

University Information Technology Services

Process

• Has a role• Is not the goal• Achieves a goal• Cannot be both rigid and flexible• Is not a substitute for judgment

A simplified view of projects fits a broader set of needs.

Page 20: Project Management 102 Pragmatic Guidelines for the Uninitiated

University Information Technology Services

Questions?

Follow up from last meeting on data storage/ security:

http://google.uconn.edu/2013/11/21/feedback-from-all-it-staff-meeting/

http://security.uconn.edu/guidance-on-cloud-services/