SLIDE 1 WORK SMART: APPLYING PROJECT MANAGEMENT TECHNIQUES TO LIBRARY PROJECTS
MICHAEL PERRY NORTHWESTERN UNIVERSITY LIBRARY
SLIDE 2 ABOUT ME
Michael Perry Head of Assessment and Planning Northwestern University Libraries michael.perry@northwestern.edu Previous Position: Collection Services Project Manager
- 6+ years project management experience
- Certificate in Project Management from
Northwestern School of Professional Studies
- Certified Scrum Master
- Member of the Project Management Institute (PMI)
SLIDE 3 WHAT WE’RE TALKING ABOUT
What is a Project?
emporary (defined beginning and end)
- Unique (not routine with a singular goal)
What is Project Management?
- Applying knowledge, skills, tools, and techniques to
project activities to meet requirements
- Many different schools of thought regarding Project
Management:
- Traditional Project Management
- Agile Project Management
SLIDE 4 TRADITIONAL PROJECT MANAGEMENT
- A Guide to the Project Management Boyd of Knowledge
(PMBOK)
- The Project Management Institute
- Process Groups
- Knowledge Areas
- Inputs / Outputs
SLIDE 5 PROJECT CONSTRAINTS
Quality Scope
SLIDE 6
WHAT IS SCOPE?
What is this project trying to accomplish? The elevator pitch for your project. Reference for all decisions about project changes.
SLIDE 7
PROJECT PROCESS GROUPS
Initiating
Planning Executing Monitoring / Controlling
Closing
SLIDE 8
PROJECT KNOWLEDGE AREAS
Human Resource Management Communications Management Risk Management Procurement Management Stakeholder Management Integration Management Scope Management Time Management Cost Management Quality Management
SLIDE 9 PROCESS GROUPS AND KNOWLEDGE AREAS
Initiating Planning Executing Monitoring Controlling Integration Project Charter Project Plan Closing Docs Scope WBS Time Cost Budget Quality HR HR Plan Comms Comms Plan Risk Risk Plan Procurement Stakeholder Stakeholder Plan
SLIDE 10 INPUTS / OUTPUTS (TEMPLATES)
- Project Charter
- Project Plan
- Work Breakdown Structure (WBS)
- Cost/Procurement Plan
- HR Plan
- Communication Plan
- Risk Plan
- Stakeholder Plan
- Scope planning document – “What are you trying to do?”
- Version Control / Analysis Document – “How do we do it?”
- Task List / Responsibilities – “Who does what?”
- Budget /
Vendor Info – “$$$$”
eam Structures / Outside Expertise – “Who do we need?”
- Project updates – “Meetings, Emails, Reports”
- Qualitative / Quantitative analysis – “What could go wrong?”
- Interested parties – “Who needs to know?”
SLIDE 11
WHERE HAVE I USED THIS?
Ideal for projects where you have a well
documented outcome
ILS Migration Building Renovation
SLIDE 12 AGILE PROJECT MANAGEMENT
- Created in response to failed software
development project
- Designed to constantly deliver value
to stakeholders
- Accomplished through the use of time
boxed sprints Agile Manifesto Individuals and interaction over processes and tools Working software over comprehensive
documentation
Customer collaboration over contract negotiation Responding to change over following a plan Delivery Framework Envision Speculate Explore Adapt Close
SLIDE 13 SCRUM
- Fixed Roles
- Scrum Master
- Product Owner
- Development T
eam
- Fixed Meetings
- Sprint Planning Session
- Daily Scrum
- Sprint Review
- Sprint Retrospective
https://www.mountaingoatsoftware.com/agile/scrum/images
SLIDE 14
USER STORIES
As a……. I want to……. So that I can ……. Why is this useful? Helps you define
what ‘done’ is
SLIDE 15
WHERE HAVE I USED THIS?
Ideal for projects when you have an idea of
the outcome but have lots of unknowns
Repository Development Classification Change
SLIDE 16
PROJECT MANAGEMENT SKILLS
Organization Communication Decision Making Time Management Negotiation Leadership Motivation
SLIDE 17
PROJECT MANAGEMENT TOOLS
A project often contains too
many moving parts for any one person to keep in mind.
Use of aid in keeping track of
who is doing what is essential for project success.
Microsoft Project Trello Basecamp Jira Agile Spreadsheet Whiteboard / Post-It Notes
SLIDE 18 REFERENCES
Books
- Highsmith, J. A. (2011). Agile project management:
Creating innovative products. Upper Saddle River: Addison-Wesley.
- Project Management Institute. (2004). A guide to the
project management body of knowledge (PMBOK guide). Newtown Square, Pa: Project Management Institute.
- Schwalbe, K. (2014). Information technology project
- management. Boston, MA: Course T
echnology.
Websites
- Project Management Institute - http://www.pmi.org/
- Mountain Goat Software (Agile) -
https://www.mountaingoatsoftware.com/
- http://standardmethod.net/
SLIDE 19 QUESTIONS?
MICHAEL.PERRY@NORTHWESTERN.EDU
