Download as PDF, PPTX
Uploaded byNicolas Emanuel Liso Fabbri
nicolas emanuel liso fabbri_project management
The document outlines a software project management course, covering objectives, course content, evaluation methods, and necessary resources. It discusses project management principles, tools, skills, phases, and common errors, emphasizing the importance of effective communication and planning. It also touches on various software metrics and methodologies for quality assurance and risk management.
More Related Content
Similar to nicolas emanuel liso fabbri_project management
nicolas emanuel liso fabbri_project management
- 1. Software Project Management SoftwareProject Management
- 2. Objectives Objectives z Introduce studentsto a variety of approaches and techniques in SPM z Use current SPM tools z Develop new SPM ideas z Document reading, experiences and ideas z Improve writing and presentation skills
- 3. Today Today z Introduction toSE 362 z Fundamentals of Project Management z Introduction to Software Project Management
- 4. Course Outline Course Outline zIntroduction to PM and SPM z Software models and process improvement z Project planning, scheduling, estimation z Personnel and project organization z Change management, monitoring & control z Protocols and standards z Software QA and risk management
- 5. Workload and Evaluation Workloadand Evaluation z Six assignments (30%) z Midterm (20%) z Final Exam (50%) z In-class presentations, critiques, discussion z Groupwork for three of the assignments
- 6. Textbooks Textbooks z Recommended Text(Free, in the library!) Quality Software Project Management, Futrell & Shafer z Lots of Other Texts (Widely varying content) Rapid Development, Steve McConnell Information Technology Project Management, Kathy Schwalbe IT Project Management, Jack Marchewka Software Engineering Project Management, edited by Richard H. Thayer Software Project Survival Guide, Steve McConnell
- 7. Format Format z Essentials ofsoftware project management z Research and textbook readings and writing z Real-world case studies z Industry visitors z Highly interactive
- 8. My Background My Background zCivil Engineering z Information Systems Management z 15 years each in industry and academia z 1 year with KPMG, IT Consulting z Projects of all shapes and sizes – health, construction, government
- 9. PM Profession PM Profession zProfessional Organizations – Project Management Institute (PMI) (pmi.org) – Software Engineering Institute (SEI) – IEEE Software Engineering Group z Certification – PMI PMP z The “PMBOK” – PM Body of Knowledge
- 10. Project Management Skills ProjectManagement Skills z Leadership z Communications z Problem Solving z Negotiating z Influencing the Organization z Mentoring z Process and technical expertise
- 11. Software Project Management SoftwareProject Management Management Project Management Software Project Management
- 12. Some PM History SomePM History z 1970’s: Early PM ideas and software – military, defense, construction industry – Fred Brooks, The Mythical Man-Month z 1980’s: SPM, TQM z 1990’s: Large shift to PM-based models – 1990-93: Re-engineering, self-directed teams – 1996-99: Risk mgmt, project offices z 2000’s: Global projects
- 13. Project Management Project Management zWhat’s a project? z PMI definition – A project is a temporary endeavor undertaken to create a unique product or service z Progressively elaborated – With repetitive elements z A project manager – Analogy: conductor, coach, captain
- 14. Project vs. Program Projectvs. Program Management Management z What’s a ‘program’? z Mostly differences of scale z Often a number of related projects z Longer than projects z Definitions vary
- 15. Interactions / Stakeholders Interactions/ Stakeholders z As a PM, who do you interact with? z Project Stakeholders – Project sponsor – Executives – Team (developers and maybe others) – Customers – Contractors (as needed) – Functional managers
- 16. PM Tools: Software PMTools: Software z Low-end – Basic features, tasks management, charting – MS Excel, Milestones Simplicity z Mid-market – Handle larger projects, multiple projects, analysis tools – MS Project (approx. 50% of market) z High-end – Very large projects, specialized needs, enterprise – AMS Realtime – Primavera Project Manager
- 17. Tools: Gantt Chart Tools:Gantt Chart
- 18. Tools: Network Diagram Tools:Network Diagram
- 19. PMI’s 9 KnowledgeAreas PMI’s 9 Knowledge Areas 1. Project integration management 2. Scope 3. Time 4. Cost 5. Quality 6. Human resource 7. Communications 8. Risk 9. Procurement
- 20. Strategy Strategy z Classic MistakeAvoidance z Development Fundamentals z Risk Management z Schedule-Oriented Practices
- 21. Four Project Dimensions FourProject Dimensions z People z Process z Product z Technology
- 22. Trade Trade- -off Triangle off Triangle zFast, cheap, good. Choose two.
- 23. Trade Trade- -off Triangle off Triangle zKnow which of these are fixed & variable for every project
- 24. People People z “It’s alwaysa people problem.” Gerald Weinberg, The Secrets of Consulting z Developer productivity: 10-to-1 range - Improvements: - Team selection - Team organization – Motivation
- 25. People …2 People …2 zOther success factors – Matching people to tasks – Career development – Balance: individual and team – Clear communication
- 26. Process Process z Is processstifling? z Two Types: Management & Technical z Development fundamentals z Quality assurance z Risk management z Lifecycle planning
- 27. Process …2 Process …2 zCustomer orientation z Process maturity improvement z Rework avoidance z Avoid abuse by neglect
- 28. Product Product z The “tangible”dimension z Product size management z Product characteristics and requirements z Feature creep management
- 29. Technology Technology z Often theleast important dimension z Language and tool selection z Value and cost of reuse
- 30. Planning Planning z Determine requirements zDetermine resources z Select lifecycle model z Determine product features strategy
- 31. Tracking Tracking z Cost, effort,schedule z Planned vs. Actual z How to handle when things go off plan?
- 32. Measurements Measurements z Actual (Todate) and Projected – Cost – Schedule – Effort – Product features
- 33. Measurements …2 Measurements …2 zAlternatives – Earned value analysis – Defect rates – Productivity (ex: SLOC) – Complexity (ex: function points)
- 34. Technical Fundamentals Technical Fundamentals zRequirements z Analysis z Design z Construction z Quality Assurance z Deployment
- 35. Project Phases Project Phases zAll projects can be divided into phases z Project Life Cycle is all phases together z Each phase marked by Deliverables z Same for software project phases
- 36.
- 37. Software Project Management SoftwareProject Management z Key Issues: Cost, Quality, Time z Software Project Planning z Software Project Control
- 38. Software Project Planning SoftwareProject Planning Software Requirements Engineering 1. Users’ needs, goals, expectations 2. Prototyping strategy 3. Software requirements specifications 4. Requirements traceability method
- 39. Software Project Planning SoftwareProject Planning - - 2 2 Project Plan Development 1. Activities, tasks 2. Cost estimation 3. Schedule, finish date
- 40. Software Project Planning SoftwareProject Planning - - 3 3 Risk Management 1. Anticipate potential problems 2. Mitigate or avoid the problems 3. Track existing and potential problems
- 41. Software Project Planning SoftwareProject Planning - - 4 4 Incremental Release Process Model 1. Provide periodic demonstrations 2. Reach short-term goals 3. Check progress towards long-term goals
- 42. Software Project Control SoftwareProject Control Work Package Development 1. Work Breakdown Structures (WBS) 2. Work Package Specifications 3. Binary Tracking Technique 4. Earned Value Tracking Technique, comparing to planned values
- 43. Software Project Control SoftwareProject Control - - 2 2 Software Metrics 1. Product metrics 2. Process metrics Necessary for planning and control
- 44. Software Project Control SoftwareProject Control - - 3 3 Software Configuration Management 1. Identify software components 2. Track component changes 3. Track documentation z Control software evolution
- 45. Software Project Control SoftwareProject Control - - 4 4 Software Quality Assurance 1. Use a SQA process 2. Use engineering standards Peer Reviews 1. Walkthroughs 2. Inspections
- 46. Software Project Control SoftwareProject Control - - 5 5 Verification and Validation 1. Quality 2. Quantity Software Engineering Assessment 1. Validate organizational capability 2. Identify software process improvements
- 47. Software Project Phases SoftwareProject Phases
- 48. Project Phases A.K.A. ProjectPhases A.K.A.
- 49. Classic Mistakes Classic Mistakes zSeductive Appeal z Types – People-Related – Process-Related – Product-Related – Technology-Related
- 50. People People- -Related Mistakes Related Mistakes zUndermined motivation z Weak personnel – Weak vs. Junior z Uncontrolled problem employees z Heroics z Adding people to a late project
- 51. People People- -Related Mistakes …2 RelatedMistakes …2 z Noisy, crowded offices z Customer-Developer friction z Unrealistic expectations z Politics over substance z Wishful thinking
- 52. People People- -Related Mistakes …3 RelatedMistakes …3 z Lack of effective project sponsorship z Lack of stakeholder buy-in z Lack of user input
- 53. Process Process- -Related Mistakes Related Mistakes zOptimistic schedules z Insufficient risk management z Contractor failure z Insufficient planning z Abandonment of plan under pressure
- 54. Process Process- -Related Mistakes …2 RelatedMistakes …2 z Wasted time during fuzzy front end z Shortchanged upstream activities z Inadequate design z Shortchanged quality assurance
- 55. Process Process- -Related Mistakes …3 RelatedMistakes …3 z Insufficient management control z Frequent convergence z Omitting necessary tasks from estimates z Planning to catch-up later z Code-like-hell programming
- 56. Product Product- -Related Mistakes Related Mistakes zRequirements gold-plating – Gilding the lily z Feature creep z Developer gold-plating – Beware the pet project z Push-me, pull-me negotiation z Research-oriented development
- 57. Technology Technology- -Related Mistakes Related Mistakes zSilver-bullet syndrome z Overestimated savings from new tools and methods – Fad warning z Switching tools in mid-project z Lack of automated source-code control
- 58. References References z ACM Conferences zICSE z SEI z IEEE Computer Society Press z IEEE Computer z Journal of Systems and Software Sciences
- 59. Standards Standards z IEEE 1058,Standards for SPM Planning z ACM z CSA z ISO z SEI’s CMM z National Bureau of Standards
- 60. Software Software z PERT/Gantt/CPM Scheduling zWork Breakdown Structure (WBS) z COCOMO II Model Definition Manual z Sim SE z Problems and Programmers
- 61. Homework Homework z Assignment 1 –Reading 56 pages – Thinking – Writing one page z Choose group partners z Start thinking about Assignment 2