Software Project Management, Schemes and Mind Maps of Software Project Management

Download Software Project Management and more Schemes and Mind Maps Software Project Management in PDF only on Docsity! Software Project Management Objectives Introduce students to a variety of approaches and techniques in SPM Use current SPM tools Develop new SPM ideas Document reading, experiences and ideas Improve writing and presentation skills Workload and Evaluation Six assignments (30%) Midterm (20%) Final Exam (50%) In-class presentations, critiques, discussion Groupwork for three of the assignments Textbooks Recommended Text (Free, in the library!) Quality Software Project Management, Futrell & Shafer 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 Format Essentials of software project management Research and textbook readings and writing Real-world case studies Industry visitors Highly interactive Project Management Skills Leadership Communications Problem Solving Negotiating Influencing the Organization Mentoring Process and technical expertise software Project ee | Management "Project / (sem -\ Project \e ay, } Sy) Some PM History 1970’s: Early PM ideas and software – military, defense, construction industry – Fred Brooks, The Mythical Man-Month 1980’s: SPM, TQM 1990’s: Large shift to PM-based models – 1990-93: Re-engineering, self-directed teams – 1996-99: Risk mgmt, project offices 2000’s: Global projects Interactions / Stakeholders As a PM, who do you interact with? Project Stakeholders – Project sponsor – Executives – Team (developers and maybe others) – Customers – Contractors (as needed) – Functional managers 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 Tools: Gantt Chart = E let) JB} Ele Ede view Insert Format Tools Project window Help BI >/ joe S6Re/sm acl“ \el= [2 S&B | no croup -|RaFr lea. | er ee Peder ed (© & = show~ | ara -e -|Bs2 vu S | all tasks j [ Team of 2-3 senior developers on board Tack Heme [Buretion [Stare ne 2002, uty 2002 I ‘August 200 | ishehsl[sbe| 114 [7 fo hs hess bs sisi] [e1s ha hshs Beginning of Project Odays Sat 61502 | @ 545 Project launchiveasthlity study 26days| Mon 6ATM2 Key project decision-maker identified Sdays| Mon 67/02 Vision statement crested, reviewed, and baselined 2days) Mon 6/24/02 Business case for the software established ‘days Wed 62602 Preliminary effort and schedule targets created, reviewed, ar, 5 days Tue 772702 [Tran ct2-Sseniordevelonersonboard 2 avs Tue 73/02, Change Control Plan created, reviewed, and baselined Sa days Thu 7/1402, Inia Top 11 Rinks | int created, reviewed, and! baselines Adays) Wee 27M Software Project Log started Tday Mon 722m2 Project launch#fcasibility study complete Odays Mon 7/2202 vel 722 El Preliminary requirements development 24days) Tue #232 GA lead on board Zaye) Tue 7/2002 Documentation lead on hoard 2days) Thu #/25/02 Key Users lertined and interviewed Sdays) Mon 7/28/02 eee Simple user-interface prototype crested, reviewed by users) 2 days Thu 8/02 oo User Intertace Style Guide created, reviewed, and baselned 6 days Mon BU, First project estimstes (accurate to +100%, -50%) crested, re. 2days| ‘Tue 6/3702 Preiminery Software Development Plan crested, reviewed,al| Sdays| Thu 8/02 Top 10 Risks List undated 2days| Tue 6/20/02 Software Project Log updated 2days) Thu 82202 Preliminary requirements development complete Odays Fri gi2302 Detailed requirements development 18days| Mon a26m2 Detsiled user-intertace prototype created, reviewed, andbas, Sdays| ‘Mon 8/26/02 User Menual/Specification crested, reviewed, and baseined | 4 days Thu 15/02 Software Gualty Assurance Plan crested, reviewed, andbe Sdays| Wed 8/14 702 _ Driaing Stare Dreenomert Pon error reviewer. sro| Panwa Mon AMBIT = . [Ready Ir [eet (ears: [worm [Scr [own Strategy Classic Mistake Avoidance Development Fundamentals Risk Management Schedule-Oriented Practices Four Project Dimensions People Process Product Technology Trade-off Triangle Fast, cheap, good. Choose two. People …2 Other success factors – Matching people to tasks – Career development – Balance: individual and team – Clear communication Process Is process stifling? Two Types: Management & Technical Development fundamentals Quality assurance Risk management Lifecycle planning Process …2 Customer orientation Process maturity improvement Rework avoidance Avoid abuse by neglect Planning Determine requirements Determine resources Select lifecycle model Determine product features strategy Tracking Cost, effort, schedule Planned vs. Actual How to handle when things go off plan? Measurements Actual (To date) and Projected – Cost – Schedule – Effort – Product features Project Phases All projects can be divided into phases Project Life Cycle is all phases together Each phase marked by Deliverables Same for software project phases Lifecycle Relationships Business Life Cycle Policy Needs Project _ Product in Planning | Identification | Conception Realization Service Disposal !Product Life Cycle Feasibility | Acqusistion Operations Disposal roject Life Cycle Concept | Development | Implementation | Termination Software Project Management Key Issues: Cost, Quality, Time Software Project Planning Software Project Control Software Project Planning - 3 Risk Management 1. Anticipate potential problems 2. Mitigate or avoid the problems 3. Track existing and potential problems Software Project Planning - 4 Incremental Release Process Model 1. Provide periodic demonstrations 2. Reach short-term goals 3. Check progress towards long-term goals Software Project 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 Software Project Control - 4 Software Quality Assurance 1. Use a SQA process 2. Use engineering standards Peer Reviews 1. Walkthroughs 2. Inspections Software Project Control - 5 Verification and Validation 1. Quality 2. Quantity Software Engineering Assessment 1. Validate organizational capability 2. Identify software process improvements Software Project Phases Software |, Concept L. Requirements Analysis Architectural . ‘am Design L. Detailed _ Design L Coding and Debugging L,| Systems Testing Deployment & Maintenance People-Related Mistakes Undermined motivation Weak personnel – Weak vs. Junior Uncontrolled problem employees Heroics Adding people to a late project People-Related Mistakes …2 Noisy, crowded offices Customer-Developer friction Unrealistic expectations Politics over substance Wishful thinking People-Related Mistakes …3 Lack of effective project sponsorship Lack of stakeholder buy-in Lack of user input Process-Related Mistakes …3 Insufficient management control Frequent convergence Omitting necessary tasks from estimates Planning to catch-up later Code-like-hell programming 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 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 Software PERT/Gantt/CPM Scheduling Work Breakdown Structure (WBS) COCOMO II Model Definition Manual Sim SE Problems and Programmers Homework Assignment 1 – Reading 56 pages – Thinking – Writing one page Choose group partners Start thinking about Assignment 2