Software Process Training

Size: px

Start display at page:

Download "Software Process Training"

Winifred Martin
8 years ago
Views:

1 Dr. Ernest Wallmüller Wolfgang Höh Rule 16 Integrated Project Management Qualität & Informatik Copyright Qualität & Informatik 2005

2 Context QA Management process areas Engineering & Support process areas Organization s Std. es Lessons Learned, Performance Data Project s Defined Coordination, commitments, issues; Product Architecture for Structuring Teams Coordination & collaboration; Shared vision & IT structure IT mgmt for engineering processes; Integrated work environment people & practices Identified risks IT Risk Taxonomies & Parameters, Status, Mitigation, and Corrective Action Basic Project Management process areas Copyright Qualität & Informatik / 2

3 - Policy / Scope / Purpose QA! Policy For AVL it is important to establish a project management which works according to defined processes. To improve the uniformity of project s defined processes these should be deviated from the organizational standard processes.! Scope All SW producing units in AVL SBU MES.! Purpose The purpose of is to establish and manage the project and the involvement of the relevant stakeholders according to an integrated and defined project s process, which is tailored from the organization s set of standard process rules. Copyright Qualität & Informatik / 3

Exercise: Familiarization QA! Method: Plenum! Timing: 20! Form: Brainstorming and discussion! Documents: none! Deliverable: Documentation on flipchart (trainer)! Questions: I.

4 Exercise: Familiarization QA! Method: Plenum! Timing: 20! Form: Brainstorming and discussion! Documents: none! Deliverable: Documentation on flipchart (trainer)! Questions: I. How do we know that the process is performing well? II. Who of you has experiences with this process? Which one? III. What are the most relevant work products? Copyright Qualität & Informatik / 4

5 Exercise: Roles, Activities, Work Products QA! Method: Individual! Timing: 10! Form: Individual elaboration! Documents: Rule 16; form: next foil! Deliverable: Filled in form Question: I. Based on your experience, the prior discussion and the process definition list the involved roles, the performed activities, and the produced work products. Copyright Qualität & Informatik / 5

6 Roles, Activities, Work Products QA Roles Activities Work Products Copyright Qualität & Informatik / 6

7 Roles, Activities, Work Products QA Roles PL-DP HOD Stakeholders Activities Establish the Project s defined Use Organizational Assets for Planning Project Activities Integrate Plans Manage the Project using the Integrated Plans Contribute to the Organizational Assets Manage Stakeholder Involvement Manage Dependencies Resolve Coordination Issues Work Products Project work product plan Lessons learned report Findings and actions list Copyright Qualität & Informatik / 7

8 with Practices QA Contribute to the OPAL Use Org. Assets for Planning Proj. Activities Manage the Project using the Integrated Plans Establish the Project s def. Integrate Plans Manage Stakeholder Involvement Manage Dependencies Resolve Coordination Issues Copyright Qualität & Informatik / 8

9 QA Tasks Practice Task Work Products Establish the Project s def. Contribute to the OPAL Use the Project s defined Tailor the selected Software Development Contribute to the OPAL Project work product plan Lessons learned report Copyright Qualität & Informatik / 9

10 QA Tasks Practice Task Work Products Coordinate and Collaborate with Relevant Stakeholders Manage Stakeholder Involvement Resolve Coordination Issues Collect and monitor all relevant commitments Resolve deviations from commitments Identify critical dependencies and address them to the relevant stakeholders Findings and actions list of relevant commitments Findings and actions list of resolved deviations Findings and actions list of critical dependencies Copyright Qualität & Informatik / 10

11 Exercise: Task Description QA! Method: Group work! Timing: 30 group work, 15 presentation & discussion (comparative discussion of group results)! Form: Group elaboration! Documents: Rule 16: Rule 23: Rule 27:! Deliverable: Task description on flipchart! Question: I. Describe the selected task _T01 Tailor the selected Software Development according to the tailoring guidelines using the presented description technique ("next foil). Copyright Qualität & Informatik / 11

12 Task Description Technique QA Input ID Task Name Description Roles Tools Method/Technique Output Copyright Qualität & Informatik / 12

13 Task Details Tailor the selected Software Development QA Input OPAL Customer requirements Organizational process needs and objectives Operational environment Business environment _T01 Roles PL-DP: Tailor the selected Software Development Description Document the project s defined process: The Project work product plan documents which parts of the Software Development es are used and which are not. Project specific agreements and definitions are made. Responsible for task _T01 Tools Template Template Project_WorkProduct_Plan.xlt Method/Technique Base on P (ev. adapted to Rule 27 ) Rule 23 Best Practices/Lessons-learned/ Output Project work product plan (accepted Project s defined ) Copyright Qualität & Informatik / 13

14 The ing QA Project Information Organization Inputs External Inputs Identify Project Characteristics Project Tech. Requirements Bldg Blocks & Tailoring Rules Acquisition Requirements Project Characteristics Choose & Tailor Building Blocks Project Defined Software Tailored Project Plan Specific Development Copyright Qualität & Informatik / 14

15 Tailoring Guidance QA Characteristic Software Project Effort Project Type Number of Interfaces (External) Project Type Software Project Effort Project Risk Project Type Quantification < 20 MW Further Release 0 Further Rel. < 5 MY Low Further Release with dynamic Requirement Set Area URS, SRS: URS/SRS in a simple form, eg. descriptive text in CQ Entry or a simple Word document P is omitted Monitoring is done in project status meetings and documented in Meeting Reports P DR1 and DR2 are not necessary. Interface document (SID) no necessary P DR4 is omitted Effect on Task/WP URS in ClearQuest P DR4 is omitted P DR Protocols can be tailored Monitoring of requirements progress and efforts Copyright Qualität & Informatik / 15

16 QA Tasks Practice Task Work Products Identify Project Characteristics Make Tailoring Decisions Identify Project Characteristics Make Tailoring Decisions Project Characteristics Document Tailored Project Plan (with rationales) Copyright Qualität & Informatik / 16

17 Rule 16: Work Products and Templates QA WP Id Type Description Resp. Link to Template _W01 M Project Characteristics Document PL-DP Template Project_Characteristics.xlt _W02 M Tailored Project Plan PL-DP Template Project_WorkProduct_Plan.xlt Copyright Qualität & Informatik / 17

18 Project Types 1/2 QA There are 4 ways to develop/deliver SW is for a customer project: a) Customer projects gets one or more already released SW product(s) b) Customer specific extensions in addition to standard SW products are required and developed with an upcoming SW development project (P for main- or subrelease) c) Customer specific extensions in addition to standard SW products are required, they are developed in a separate development environment (CSE branch in source code management system); Results are merged into the next subrelease/mainrelease of the affected product in order minimize future maintenance effort Copyright Qualität & Informatik / 18

19 Project Types 2/2 QA a) Customer specific extensions in addition to standard SW products are required, they are developed in a separate development environment (CSE branch in source code management system); Results are N merged into the next subrelease/mainrelease of the affected product. In this case, maintenance is done by the team, who developed the CSE branch during warranty and if the customer ordered specific maintenance Copyright Qualität & Informatik / 19

20 Rule 16: Work Products and Templates QA WP Id Type Description Task Id Resp. Link to Template _W01 M Project work product plan _T01 PL-DP Template Project_WorkProduct_Plan.xlt _W02 M Lessons Learned Report _T02 PL-DP Template Lessons_learned_and_best_practices.xls _W03 M Findings and Actions List _T03, _T04, _T05 PL-DP Template P_Projects_Action_List.xlt Copyright Qualität & Informatik / 20

21 Rule 16: Concluding Discussion QA What was important for you concerning this Rule? Copyright Qualität & Informatik / 21

22 Any Questions QA Copyright Qualität & Informatik / 22

Software Process Training

Software Process Training Dr. Ernest Wallmüller Wolfgang Höh Rule 6 Development Qualität & Informatik www.itq.ch Copyright Qualität & Informatik 2005 Context Ver Product & product component requirements Alternative solutions Product