Your SlideShare is downloading. ×
Simple Project Management
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×
Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

Simple Project Management

982
views

Published on

Slides use to support a hands on workshop for integrating Agile into your higher ed teams.

Slides use to support a hands on workshop for integrating Agile into your higher ed teams.

Published in: Business, Technology

0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
982
On Slideshare
0
From Embeds
0
Number of Embeds
3
Actions
Shares
0
Downloads
12
Comments
0
Likes
0
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide

Transcript

  • 1. Project Management Thinking
    Simple, Agile.
  • 2. About me.
    Sault Ste Marie, ON
    Assoc. Director VeloCity
    2 kids (boy/girl)
    BA, Msc
    Co-founder
  • 3. About you?
  • 4. Observations
    Project Management: designed by engineers for engineers
    Software is designed to support specific types of projects and people
    Project Management is a people process
  • 5.
  • 6. A Project is… “a temporary endeavor undertaken to create a unique product, service, or result”
    – PMBOK Guide (2004)
  • 7. Typical project
    Building a few web pages for a department.
    Developing a simple web application that collects student information.
    Using Twitter/Facebook/Ning for whatever specific reason*
    Recruiting cycle for students.
  • 8. A Project is… “ongoing, with many false starts and chronic scope creep. Governed by committee(s), success is not often tangible.”
    – Higher Ed.
  • 9. The Chaos
    Conflicting expectations
    Isolated or independent departments
    “This is my ‘third hat’ I am wearing”
    Committees.
    Never ending change requests.
  • 10. Essential tool #1 – Text editor.
  • 11. Project definition
    First meeting needs a “memorandum of agreement”
    Define the goals, objectives, and/or outcomes
    Sign it.
  • 12. Triple Constraint
    Scope
    Time
    Cost
  • 13. Triple Constraint
    What am I trying to build/deliver?
    How long will it take?
    How much will it cost (time = money, etc)?
  • 14.
  • 15. Follow a process, deliver a product.
  • 16. # S: (adj) agile, nimble, quick, spry (moving quickly and lightly) "sleek and agile as a gymnast"; "as nimble as a deer"; "nimble fingers"; "quick of foot"; "the old dog was so spry it was halfway up the stairs before we could stop it"
    - http://wordnetweb.princeton.edu/perl/webwn?s=agile
  • 17. Image from http://www.flickr.com/photos/18091975@N00/
  • 18.
  • 19. From http://www.flickr.com/photos/orcmid/3879384912/
  • 20.
  • 21. What about software?
    Web based or not?
    How many people are using it with me?
    Privacy implications?
    Cost.
  • 22. There are three choices.
    Microsoft Project (larger teams)
    OmniPlan (for the mac users)
    Basecamp*
  • 23.
  • 24. Microsoft Project is bad
    Forces you into a resource driven process
    Assumes people will do the task assigned
    Full time job to use the tool efficiently
    Expertise is required
  • 25. Gantt charts
    Allow you to break down the task list to chunks
    You can assign resources
    You can management from a central hub
  • 26. Hosted solutions
    Good: Allow for more flexibility on access
    Good: Monthly costs, do not go for per user model
    Bad: Does not connect with your directory service (ADS, LDAP, etc)
    Bad: You don’t know where you data is unless you install something yourself*
  • 27. Ground rules
    Question the use of gantt charts
    Organize into short iterations
    Requirement-based approach
    Schedule tasks involving external groups
    http://bit.ly/psweb_agile
  • 28. Track the project.
  • 29.
  • 30.
  • 31.
  • 32. Use a process that works for you and don’t let software dictate how you do it.
  • 33. Contact me.
    Jesse Rodgers
    Associate Director, VeloCity -- University of Waterloo
    Blog: http://whoyoucallingajesse.com
    Twitter: http://twitter.com/jrodgers
    Email: jrodgers@uwaterloo.ca

×