Software Project Management Slides - Syrian Private University - PDF

Syrian Private University Software Project Management Instructor: Dr. Mouhib Alnoukari  Software Project Initiation Software Project Management– Syrian Private University – Instructor: Dr. Mouhib Alnoukari 2  Project Initiation Purpose Initiate...

Syrian Private University Software Project Management Instructor: Dr. Mouhib Alnoukari  Software Project Initiation Software Project Management– Syrian Private University – Instructor: Dr. Mouhib Alnoukari 2  Project Initiation Purpose Initiate the project and identify the higher level information needed for the project management plan. Based on information provided from the Statement of Work (SOW) document or any other equivalent documentation from the pre-sales phase. Identify standards to develop work products, Life Cycle Model (LCM) for software development and tools to be used on the project. Software Project Management– Syrian Private University – Instructor: Dr. Mouhib Alnoukari 3  Project Charter After deciding what project to work on, it is important to let the rest of the organization know. A project charter is a document that formally recognizes the existence of a project and provides direction on the project’s objectives and management. Key project stakeholders should sign a project charter to acknowledge agreement on the need and intent of the project; a signed charter is a key output of project integration management. Software Project Management– Syrian Private University – Instructor: Dr. Mouhib Alnoukari 4  Preliminary Scope Statements A scope statement is a document used to develop and confirm a common understanding of the project scope. It is an important tool for preventing scope creep: – The tendency for project scope to keep getting bigger. A good practice is to develop a preliminary or initial scope statement during project initiation and a more detailed scope statement as the project progresses. Software Project Management– Syrian Private University – Instructor: Dr. Mouhib Alnoukari 5  Contents of a Preliminary Scope Statement Project objectives Initial list of defined risks Product or service Summary of schedule requirements and milestones characteristics Rough order of magnitude Project boundaries cost estimate Deliverables Configuration management Product acceptance criteria requirements Project assumptions and Description of approval constraints requirements Organizational structure for the project Software Project Management– Syrian Private University – Instructor: Dr. Mouhib Alnoukari 6  Stakeholder Analysis A stakeholder analysis documents important (often sensitive) information about stakeholders such as: – Stakeholders’ names and organizations. – Their roles on the project. – Unique facts about each stakeholder. – Their level of influence on and interest in the project. – Suggestions for managing relationships with each stakeholder. Software Project Management– Syrian Private University – Instructor: Dr. Mouhib Alnoukari 7  Sample Stakeholder Analysis Software Project Management– Syrian Private University – Instructor: Dr. Mouhib Alnoukari 8 Sample Stakeholder Analysis for Project Communications Software Project Management– Syrian Private University – Instructor: Dr. Mouhib Alnoukari 9  Managing Stakeholders ▪ Project managers must understand and work with various stakeholders. ▪ Need to devise a way to identify and resolve issues. ▪ Two important tools include: ▪ Expectations management matrix ▪ Issue log Software Project Management– Syrian Private University – Instructor: Dr. Mouhib Alnoukari 10  Expectations Management Matrix Software Project Management– Syrian Private University – Instructor: Dr. Mouhib Alnoukari 11  Issue Log Software Project Management– Syrian Private University – Instructor: Dr. Mouhib Alnoukari 12  Statement of Work (SOW) SOW Contains normally: Information about project description, objectives and scope, project contracts, assumptions, project deliverable(s), initial estimated efforts and cost. In addition to: ▪ Initial project resources ▪ Project technology and tools ▪ Initial estimated expenses ▪ Customer supplied products / services ▪ Acceptance criteria ▪ Constraints ▪ Payment schedule ▪ References Software Project Management– Syrian Private University – Instructor: Dr. Mouhib Alnoukari 13  Project Scope & Product Scope Project Scope: The work that must be performed to deliver a product, service, or result with the specified features and functions. Product Scope: The features and functions that characterize a product, service, or result. Software Project Management– Syrian Private University – Instructor: Dr. Mouhib Alnoukari 14  Assumptions Assumptions are facts that, for planning purposes, are considered to be true, real, or certain without proof or demonstrations. Assumptions should be quickly validated – converted to facts – or they become risks. Software Project Management– Syrian Private University – Instructor: Dr. Mouhib Alnoukari 15  Project: Functions, Activities and Tasks A Project has a duration and consists of functions, activities and tasks Function Project Function Activity Activity Activity Activity Activity Activity Task Task Task Task Software Project Management– Syrian Private University – Instructor: Dr. Mouhib Alnoukari 16  Functions Function: An activity or set of activities that span the duration of the project Function Project Function Activity Activity Activity Activity Activity Activity Task Task Task Task Software Project Management– Syrian Private University – Instructor: Dr. Mouhib Alnoukari 17  Functions Examples: – Project management – Configuration Management – Documentation – Quality Control (Verification and validation) – Training Question: Is system integration a project function? Mapping of terms: Project Functions in the IEEE 1058 standard are called Integral processes in the IEEE 1074 standard. Sometimes also called cross- development processes Software Project Management– Syrian Private University – Instructor: Dr. Mouhib Alnoukari 18  Tasks Function Project Function Activity Activity Activity Smallest unit of work subject to management Activity Activity Activity Small enough for adequate planning and Task Task Task Task tracking Large enough to avoid micro management Software Project Management– Syrian Private University – Instructor: Dr. Mouhib Alnoukari 19  Tasks Smallest unit of management accountability – Atomic unit of planning and tracking – Tasks have finite duration, need resources, produce tangible result (documents, code) Specification of a task: Work package – Name, description of work to be done – Preconditions for starting, duration, required resources – Work product to be produced, acceptance criteria for it – Risk involved Completion criteria – Includes the acceptance criteria for the work products (deliverables) produced by the task. Software Project Management– Syrian Private University – Instructor: Dr. Mouhib Alnoukari 20  Determining Task Size  Finding the appropriate task  Tasks must be decomposed size is problematic into sizes that allow ◦ To do lists from previous monitoring projects ◦ Work package usually ◦ During initial planning a corresponds to well task is necessarily large defined work assignment ◦ You may not know how to for one worker for a week decompose the problem or a month. into tasks at first ◦ Depends on nature of ◦ Each software work and how well task is development activity understood. identifies more tasks and modifies existing ones Software Project Management– Syrian Private University – Instructor: Dr. Mouhib Alnoukari 21  Action Item Action Item: A task assigned to a project participant – What?, Who?, When? – Heuristics for Duration: be done within two week or a week Action items should appear on the meeting agenda in the Status Section Examples of Todos: – Unit test class Foo – Develop project plan. Example of action items: – Bob posts the next agenda for the context team meeting before Sep 10, 12 noon. – The test team develops the test plan by Sep 18 Software Project Management– Syrian Private University – Instructor: Dr. Mouhib Alnoukari 22  Activities Function Project Function Major unit of work with Activity Activity Activity precise dates Activity Activity Activity Consists of smaller Task activities or tasks Task Task Task Culminates in project milestone. Software Project Management– Syrian Private University – Instructor: Dr. Mouhib Alnoukari 23  Activities  Major unit of work  Activities may be grouped  Culminates in major project into larger activities: milestone: ◦ Establishes hierarchical ◦ Internal checkpoint structure for project should not be externally (phase, step,...) visible ◦ Allows separation of ◦ Scheduled event used to concerns measure progress ◦ Precedence relations  Milestone often produces often exist among project baselines: activities ◦ formally reviewed work product ◦ under change control (change requires formal procedures) Software Project Management– Syrian Private University – Instructor: Dr. Mouhib Alnoukari 24  Work Beakdown Structure (WBS) The hierarchical representation of all the tasks in a project is called the work breakdown structure (WBS). First Version of a UML Model Work Br eakdown Struc ture Task * But Tasks are Parts of Activities. What would be a better model? Work Br eakdown Stru cture Work * * Task Activit y Software Project Management– Syrian Private University – Instructor: Dr. Mouhib Alnoukari 25  Creating WBS Two major philosophies – Activity-oriented decomposition (“Functional decomposition“) Write the book Get it reviewed Do the suggested changes Get it published – Result-oriented (“Object-oriented decomposition“) Chapter 1 Chapter 2 Chapter 3 Which one is best for managing? Depends on project type: – Development of a prototype – Development of a product – Project team consist of many unexperienced beginners – Project team has many experienced developers Software Project Management– Syrian Private University – Instructor: Dr. Mouhib Alnoukari 26  WBS Based on Project Documents (Entity-Oriented) Project Problem Project Statement RAD SDD Agreement - Write Requirements - Write Introduction - Write Design Goals - Write Constraints - Describe Functional - Write Hardware - Write Acceptance Model Software mapping Criteria - Describe Object Model -Write boundary - Promise delivery date - Describe Dynamic conditions Model - Write Data... Management - Write Open Issues... Software Project Management– Syrian Private University – Instructor: Dr. Mouhib Alnoukari 27  WBS Based on Software Process (Activity-Oriented) Project Project Planning Analysis Initiation Design - Establish guidelines - Determine WBS - Brainstorm on - Develop Models - Formulate requirements - Determine dependencies application domain - Write code with client between tasks objects - Present problems to - Establish scenarios - Write SPMP - Develop class diagram coach - Write project agreement - Assign teams to - Partition objects into - Give status reports subsystems boundary, entity and - Write RAD - Establish project control objects - Write SDD calendar - Develop use cases - Write ODD Software Project Management– Syrian Private University – Instructor: Dr. Mouhib Alnoukari 28  WBS Level of Details The level of detail of the WBS depends on the phase where the estimation is done. More WBS details ⇨ more accurate estimation. In early phases of the project, the WBS may show only lifecycle phases. Later on, the WBS may be elaborated to the level of detailed tasks. Software Project Management– Syrian Private University – Instructor: Dr. Mouhib Alnoukari 29  Project Initiation Activities 1. Analyze SOW / Pre-sales documents 2. Identify purpose and scope 3. Identify project objectives 4. Determine assumptions 5. Determine target environment 6. Identify work products 7. Identify standards 8. Define lifecycle & WBS 9. Prepare initial schedule 10.Establish CM environment Software Project Management– Syrian Private University – Instructor: Dr. Mouhib Alnoukari 30  Next Lecture Software Project Planning Software Project Management– Syrian Private University – Instructor: Dr. Mouhib Alnoukari 31