Introduction to Project Management
Download as PPTX, PDF0 likes841 views
The document provides an overview of project management, including its definitions and processes, with a focus on traditional, iterfall, and agile project management methodologies. It discusses the strengths and weaknesses of each approach, highlighting the importance of effective resource usage, flexibility, and collaboration among team members. Additionally, it outlines key concepts such as milestones, workflows, and project management tools, emphasizing the need for clear goals and structured planning.
Introduction to Project Management
- 1. Introduction toProject ManagementChris Warrencwarren@williams.edux4323 Jesup 312
- 2. What Is Project ManagementA formal process for getting things doneA scientific approach to the good old To Do listOccasionally, a pain in the buttUsually useful anyway
- 3. What Is Project ManagementTo Do ListIntuitive Gravitygo shoppingeat pizzastare at skydo a little dancesing a little song...
- 4. What Is Project ManagementProject ManagementScientific GravityProject: Purple CowTeamJayDeonJulieZinaGoalssongdancechocolateMilestonesHay – due 6/30sow seeds – Jaywater – Jayweed – Deonverify- Zinaharvest – JuliFencing – due 7/05....Cow (depends on Hay) – due 7/14find – Zinaget to quad – Jay, Julie, Deon, Zina...
- 5. Why Project ManagementIncrease likelihood of successUse resources effectivelyReduce uncertaintyPut work in a larger contextReduce stress
- 6. Traditional PM4-5 distinct phasesInitiation / visionPlanning / designExecution / developmentMonitoring / controlClosing / deploymentLots of up-front planningClean hand-off between phases
- 7. Traditional PM – Yay!Proven track recordEasy to understandEasy to applyWell suited to top-down input
- 8. Traditional PM – Boo.InflexibleKnown-result orientedHigh overheadOverwhelmingLow benefit for small projectsMissing key web / software steps
- 9. Technology Project IssuesExploratory and inventiveLOTS of testing and debuggingAdditional maintenance phaseChanging requirementsClients can be.... tricky
- 10. Technology PM - WaterfallInitiation Specification / RequirementsPlanning DesignExecution / developmentTesting and debuggingDeploymentMaintenanceThen we tweak things just a bit to get...
- 11. TheIterfallModel
- 12. Iterfall (Iterated Waterfall)Initiation Specification / RequirementsPlanning DesignExecution / DevelopmentTesting and DebuggingDeploymentMaintenance
- 13. Iterfall Project ManagementBetter, but still has some basic problemsIn response to the shortcomings of the iterfall model a relatively new style of project management has been developed...
- 14. Agile Project ManagementA P M !
- 15. Agile Project ManagementQuick software developmentSmall, tight teamsVery flexibleVery human-interaction orientedBest for non-critical projects
- 16. APM - Yay!Quick software developmentSmall, tight teamsVery flexibleVery human-interaction orientedBest for non-critical projectsBUT.....
- 17. APM... Boo?Requires experienced developersRelies on VERY frequent feedbackRelies on self-organization and self-directionLack of group expertise can enhance mistakesAnd yet....
- 18. A Middle GroundIterfall model provides larger structureover all time frameabstract milestoneseasily teachable approachclear goalsAPM provides per-step frameworkteam orientedexploratoryflexible
- 19. W I T e r f a l l
- 20. WITerfall Project ManagementInitiation – donea clear vision is last step of 1 or the first step of 2Specification (trad) – lots of helpPlanning (hybrid) – moderate helpDesign (agile) – minimal helpImplementation (agile) – minimal helpTesting and Debugging (agile) – minimal helpRelease & Hand-off (hybrid) – moderate helpMaintenance – outside WIT
- 21. Requirements & SpecificationGOAL 1: Help the sponsor develop and clarify their vision.GOAL 2: Come to a mutual understanding of what the project is.GOAL 3: Make sure the project can be completed!
- 22. PlanningMilestonesan ordered list of stagespoints along a pathTo-Do’s / Items / Steps / etc.often associated with a milestonenote especially difficult itemsnote dependencies and paralleliza-whatever... things you can do at the same time (but beware of yak shaving...)
- 23. WorkflowWorkflows are the checkpoints / sign-offs used to make sure particular tasks are done correctlyGraphic DesignTeam members reviewITS signs off Sponsor signs offDatabasesChris reviews structureTest data entryCodingProject ArchitectureDebuggingSpec ChangesFilming a Movie...
- 24. Testing and DebuggingTasks / Tickets keep track of problems discovered or enhancements requestedWhat the problem isWhen it’s dueWho’s working on itNotes about the work
- 26. Sample Web Project MilestonesProject management set upProject SpecifiedDocumentation framework set upDevelopment environment set upContent organizedBase theme chosen (WP)Functioning web sitePlaceholder content enteredVisual mockups approvedMedia preparedCustom functionality implementedTheme finishedMedia deployedFinal content in placeHelp docs completeSponsor approvalReleasedHanded off to sponsorPresentation Done
Editor's Notes
- #6: success is not guaranteed; need to know what ‘success’ means for the project; material and human resources; low uncertainty needed for planning; context of other projects, constraints, and events; know what to do when; have reasonable expectations
- #7: arose as a distinct, formal system in the 1950’s; Henrey Gantt; Henri Fayol; Frederick Winslow Taylor;
- #8: recipe-like
- #9: software and technologydevelopment projects often have additional complications that cause problems for traditional project management approaches
- #16: break the project into very small pieces; focus on very short (1-4 week) iterative cycles, each of which is a microcosm of the waterfall system; start and end with a working product; accumulate features; works well for small, tight teams of 5-9 people; gain flexibility but lose certainty
- #22: go over the handout