1 / 46

Software Project Management

Lecture # 01 Nadeem Majeed Choudhary nadeem.majeed@uettaxila.edu.pk. Software Project Management. Introduction, Fundamentals, Classic Mistakes. Today. Course basics Introductions Fundamentals Classic Mistakes. Textbooks. Required texts “Rapid Development”, Steve McConnell

aenriquez
Download Presentation

Software Project Management

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Lecture # 01 Nadeem Majeed Choudhary nadeem.majeed@uettaxila.edu.pk Software Project Management Introduction, Fundamentals, Classic Mistakes

  2. Today • Course basics • Introductions • Fundamentals • Classic Mistakes nadeem.majeed@uettaxila.edu.pk

  3. Textbooks • Required texts • “Rapid Development”, Steve McConnell • “Information Technology Project Management”, Kathy Schwalbe • These provide two very different viewpoints • In-the-trenches vs. PMI textbook perspective • Recommended reading • “Quality Software Project Management”, D. Shafer • “Software Project Survival Guide”, Steve McConnell • “Peopleware”, T. DeMarco and T. Lister nadeem.majeed@uettaxila.edu.pk

  4. Basics • Essential elements of software project management • Practical, rapid development focus • Real-world case studies • And other examples like job interviews • Highly interactive • Dry as toast? nadeem.majeed@uettaxila.edu.pk

  5. The Field • Jobs: where are they? • Professional Organizations • Project Management Institute (PMI) (pmi.org) • Software Engineering Institute (SEI) • IEEE Software Engineering Group • Certifications • PMI PMP • The “PMBOK” – PMI Body of Knowledge • Tools • MS Project nadeem.majeed@uettaxila.edu.pk

  6. Project Management Skills • Leadership • Communications • Problem Solving • Negotiating • Influencing the Organization • Mentoring • Process and technical expertise nadeem.majeed@uettaxila.edu.pk

  7. Software Project Management nadeem.majeed@uettaxila.edu.pk

  8. PM History in a Nutshell • Birth of modern PM: Manhattan Project (the bomb) • 1970’s: military, defense, construction industry were using PM software • 1990’s: large shift to PM-based models • 1985: TQM • 1990-93: Re-engineering, self-directed teams • 1996-99: Risk mgmt, project offices • 2000: M&A, global projects nadeem.majeed@uettaxila.edu.pk

  9. Project Management • What’s a project? • PMI definition • A project is a temporary endeavor undertaken to create a unique product or service • Progressively elaborated • With repetitive elements • A project manager • Analogy: conductor, coach, captain nadeem.majeed@uettaxila.edu.pk

  10. Project vs. Program Management • What’s a ‘program’? • Mostly differences of scale • Often a number of related projects • Longer than projects • Definitions vary • Ex: Program Manager for MS Word nadeem.majeed@uettaxila.edu.pk

  11. Interactions / Stakeholders • As a PM, who do you interact with? • Project Stakeholders • Project sponsor • Executives • Team • Customers • Contractors • Functional managers nadeem.majeed@uettaxila.edu.pk

  12. PM Tools: Software • Low-end • Basic features, tasks management, charting • MS Excel, Milestones Simplicity • Mid-market • Handle larger projects, multiple projects, analysis tools • MS Project (approx. 50% of market) • High-end • Very large projects, specialized needs, enterprise • AMS Realtime • Primavera Project Manager nadeem.majeed@uettaxila.edu.pk

  13. Tools: Gantt Chart nadeem.majeed@uettaxila.edu.pk

  14. Tools: Network Diagram nadeem.majeed@uettaxila.edu.pk

  15. PMI’s 9 Knowledge Areas • Project integration management • Scope • Time • Cost • Quality • Human resource • Communications • Risk • Procurement nadeem.majeed@uettaxila.edu.pk

  16. First Principles • One size does not fit all • Patterns and Anti-Patterns • Spectrums • Project types • Sizes • Formality and rigor nadeem.majeed@uettaxila.edu.pk

  17. Why Rapid Development • Faster delivery • Reduced risk • Increased visibility to customer • Don’t forsake quality nadeem.majeed@uettaxila.edu.pk

  18. Strategy • Classic Mistake Avoidance • Development Fundamentals • Risk Management • Schedule-Oriented Practices nadeem.majeed@uettaxila.edu.pk

  19. Four Project Dimensions • People • Process • Product • Technology nadeem.majeed@uettaxila.edu.pk

  20. Trade-off Triangle • Fast, cheap, good. Choose two. nadeem.majeed@uettaxila.edu.pk

  21. Trade-off Triangle • Know which of these are fixed & variable for every project nadeem.majeed@uettaxila.edu.pk

  22. People • “It’s always a people problem” Gerald Weinberg, “The Secrets of Consulting” • Developer productivity: 10-to-1 range • Improvements: • Team selection • Team organization • Motivation nadeem.majeed@uettaxila.edu.pk

  23. People 2 • Other success factors • Matching people to tasks • Career development • Balance: individual and team • Clear communication nadeem.majeed@uettaxila.edu.pk

  24. Process • Is process stifling? • 2 Types: Management & Technical • Development fundamentals • Quality assurance • Risk management • Lifecycle planning • Avoid mishandling by negligence nadeem.majeed@uettaxila.edu.pk

  25. Process 2 • Customer orientation • Process maturity improvement • Rework avoidance nadeem.majeed@uettaxila.edu.pk

  26. Product • The “tangible” dimension (concrete) • Product size management • Product characteristics and requirements • Feature creep management nadeem.majeed@uettaxila.edu.pk

  27. Technology • Often the least important dimension • Language and tool selection • Value and cost of reuse nadeem.majeed@uettaxila.edu.pk

  28. Planning • Determine requirements • Determine resources • Select lifecycle model • Determine product features strategy nadeem.majeed@uettaxila.edu.pk

  29. Tracking • Cost, effort, schedule • Planned vs. Actual • How to handle when things go off plan? nadeem.majeed@uettaxila.edu.pk

  30. Measurements • To date and projected • Cost • Schedule • Effort • Product features • Alternatives • Earned value analysis • Defect rates • Productivity (ex: SLOC) • Complexity (ex: function points) nadeem.majeed@uettaxila.edu.pk

  31. Technical Fundamentals • Requirements • Analysis • Design • Construction • Quality Assurance • Deployment nadeem.majeed@uettaxila.edu.pk

  32. Project Phases • All projects are divided into phases • All phases together are known as the Project Life Cycle • Each phase is marked by completion of Deliverables • Identify the primary software project phases nadeem.majeed@uettaxila.edu.pk

  33. Lifecycle Relationships nadeem.majeed@uettaxila.edu.pk

  34. Seven Core Project Phases nadeem.majeed@uettaxila.edu.pk

  35. Project Phases A.K.A. nadeem.majeed@uettaxila.edu.pk

  36. Phases Variation nadeem.majeed@uettaxila.edu.pk

  37. 36 Classic Mistakes • Seductive Appeal : • Seductive: good reason for decisions at the time • Types • People-Related • Process-Related • Product-Related • Technology-Related nadeem.majeed@uettaxila.edu.pk

  38. People-Related Mistakes Part 1 • Undermined motivation • Weak personnel • Weak vs. Junior • Uncontrolled problem employees • Heroics • Adding people to a late project nadeem.majeed@uettaxila.edu.pk

  39. People-Related Mistakes Part 2 • Noisy, crowded offices • Customer-Developer friction • Unrealistic expectations • Politics over substance • Wishful thinking • Cognitive dissonance (Thinking difference ) • Closing your eyes and hoping nadeem.majeed@uettaxila.edu.pk

  40. People-Related Mistakes Part 3 • Lack of effective project sponsorship • Lack of stakeholder buy-in • Lack of user input nadeem.majeed@uettaxila.edu.pk

  41. Process-Related Mistakes Part 1 • Optimistic schedules • Insufficient risk management • Contractor failure • Insufficient planning • Abandonment of plan under pressure nadeem.majeed@uettaxila.edu.pk

  42. Process-Related Mistakes Part 2 • Wasted time during fuzzy front end • Shortchanged upstream activities • Inadequate design • Shortchanged quality assurance nadeem.majeed@uettaxila.edu.pk

  43. Process-Related Mistakes Part 3 • Insufficient management controls • Frequent convergence • Omitting necessary tasks from estimates • Planning to catch-up later • Code-like-hell programming nadeem.majeed@uettaxila.edu.pk

  44. Product-Related Mistakes • Requirements gold-plating • Gilding the lily • Feature creep • Developer gold-plating • Beware the pet project • Push-me, pull-me negotiation • Research-oriented development nadeem.majeed@uettaxila.edu.pk

  45. Technology-Related Mistakes • Silver-bullet syndrome • Overestimated savings from new tools and methods • Fad warning • Switching tools in mid-project • Lack of automated source-code control nadeem.majeed@uettaxila.edu.pk

  46. Reading • McConnell: Chapters 1-4 • We covered most of Ch 3 today • Schwalbe: chapters 1-2, 11 (344-345) nadeem.majeed@uettaxila.edu.pk

More Related