OXFORD SOFTWARE ENGINEERING Software Engineering Services & Consultancy Slide 1.1© OSEL 2001 Software Project Management: MONITORING AND CONTROL SPIN -

Slides:



Advertisements
Similar presentations
OXFORD SOFTWARE ENGINEERING Software Engineering Services & Consultancy Slide 1.1 eXtreme Programming experiences with a new approach to software development.
Advertisements

MODELING THE TESTING PROCESS Formal Testing (1.0) Requirements Software Design Risk Data Approved, Debugged, Eng. Tested Code Automated Test Tools Tested.
Software Engineering CSE470: Process 15 Software Engineering Phases Definition: What? Development: How? Maintenance: Managing change Umbrella Activities:
More CMM Part Two : Details.
Procedures for CMM Level 2 Copyright, 2000 © Jerzy R. Nawrocki Quality Management.
Stoimen Stoimenov QA Engineer SitefinityLeads, SitefinityTeam6 Telerik QA Academy Telerik QA Academy.
Metrics for Process and Projects
CSCU 411 Software Engineering Chapter 2 Introduction to Software Engineering Management.
Project Change Management
Stepan Potiyenko ISS Sr.SW Developer.
University of Minho School of Engineering Centre Algoritmi Uma Escola a Reinventar o Futuro – Semana da Escola de Engenharia - 24 a 27 de Outubro de 2011.
Overview Lesson 10,11 - Software Quality Assurance
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 1 Slide 1 Project management.
10.5 Report Performance The process of collecting and distributing performance information, including status reports, progress measurements and forecasts.
1 Project Management CIS 375 Bruce R. Maxim UM-Dearborn.
©Ian Sommerville 2006Software Engineering, 8th edition. Chapter 5 Slide 1 Project management.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 5 Slide 1 Project management.
Copyright © 2014 ASTQB Presented by Rex Black, CTAL Introducing ISTQB Agile Foundation Extending the ISTQB Program’s Support Further.
OXFORD SOFTWARE ENGINEERING Software Engineering Services & Consultancy Slide 1© OSEL  - and its application to software development UK SPIN May.
Project planning. Software project management Informal definition of management – The art of getting work done through other people Software project management.
Part II AUTOMATION AND CONTROL TECHNOLOGIES
Process: A Generic View
Team Launch Introduction. Real projects are large and complex, and most software is created by teams Merely throwing people together does not result in.
COMPGZ07 Project Management Presentations Graham Collins, UCL
What is Software Engineering? the application of a systematic, disciplined, quantifiable approach to the development, operation, and maintenance of software”
Software Configuration Management
Best Practices By Gabriel Rodriguez
SESSION 4 COLLECTING EVIDENCE OF LEARNER PERFORMANCE CAT AND IT.
Resources Performance time. resources Performance time 2.
Chapter 2 소프트웨어공학 Software Engineering 임현승 강원대학교
Project Tracking. Questions... Why should we track a project that is underway? What aspects of a project need tracking?
Chapter 3: Software Maintenance Process Omar Meqdadi SE 3860 Lecture 3 Department of Computer Science and Software Engineering University of Wisconsin-Platteville.
Soft Tech Development Inc. 1 Software Project Tracking A CMM Level 2 Key Process Area Soft Tech Development Inc.
Chapter 6 : Software Metrics
Requirements Engineering CSE-305 Requirements Engineering Process Tasks Lecture-5.
Agile Methodologies: Comparative Study and Future Direction 林佳蓁 資工 4B.
These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 6/e and are provided with permission by.
Coming up: Software Engineering: A Practitioner’s Approach, 6/e Chapter 5 Practice: A Generic View copyright © 1996, 2001, 2005 R.S. Pressman & Associates,
IT Requirements Management Balancing Needs and Expectations.
Software Project Management By Deepika Chaudhary.
Software Quality Assurance
Objectives 4 Understand the importance of communication in projects 4 Understand the need and importance of project management.
Progress Monitoring for All Student Adapted from the Kentucky Systems of Interventions Guidance Document.
Software Engineering Saeed Akhtar The University of Lahore Lecture 6 Originally shared for: mashhoood.webs.com.
Chapter 4 프로세스 모델 Process Models
 Copyright ProcessVelocity, LLP Slides intended for informational purposes only. CMM and Capability Maturity Model are registered in the U.S. Patent.
OXFORD SOFTWARE ENGINEERING Software Engineering Services & Consultancy Slide 12 February 1999 Its not the model - its what you do Its not the model -
February 15, 2004 Software Risk Management Copyright © , Dennis J. Frailey, All Rights Reserved Simple Steps for Effective Software Risk Management.
Software Project Management Lecture # 2 Originally shared for: mashhoood.webs.com.
1 Monitoring and Evaluating Employee Wellness Programs.
OXFORD SOFTWARE ENGINEERING Software Engineering Services & Consultancy Slide 1.1 © Copyright OSEL 2002 Beyond Numbers SPIN September 2002.
Hussein Alhashimi. “If you can’t measure it, you can’t manage it” Tom DeMarco,
Software Testing Process
WHAT IS THE POTENTIAL EFFECT ON YOU AS A TEACHER OF STUDENTS WHO LACK MOTIVATION?
Advances In Software Inspection
Software Engineering (CSI 321) Software Process: A Generic View 1.
1 Project Management Software management is distinct and often more difficult from other engineering managements mainly because: – Software product is.
Software Project Management
Z26 Project Management Presentations Lecture 5b 9 th February 2006 Graham Collins, UCL.
OXFORD SOFTWARE ENGINEERING Software Engineering Services & Consultancy Slide 1.1 © OSEL 2005 Page 1 of 30 Analysis of Defect (and other) Data SPIN London,
Extreme Software Engineering A Hands-On Approach From Extreme Software Engineering: A Hands-On Approach Daniel H. Steinberg Daniel W. Palmer.
©2008 Pearson Education, Inc., Upper Saddle River, NJ. All rights reserved. This material is protected under all copyright laws as they currently exist.
OXFORD SOFTWARE ENGINEERING Software Engineering Services & Consultancy Slide 1© OSEL 2008 CMMI and Metrics BCS SPIN SG, 19 February 2008 Clifford Shelley.
Adaptive Software Development Process Framework. Version / 21 / 2001Page Project Initiation 2.0 Adaptive Cycle Planning 5.0 Final Q/A and.
OXFORD SOFTWARE ENGINEERING Consulting Software Engineers © OSEL 2009 Page 1 of 9 A first review of the SPI Manifesto BCS SPIN, 14 December 2009 C. C.
Software Project Configuration Management
CS4311 Spring 2011 Process Improvement Dr
Introducing ISTQB Agile Foundation Extending the ISTQB Program’s Support Further Presented by Rex Black, CTAL Copyright © 2014 ASTQB 1.
Refactoring.
Software Project Management
Presentation transcript:

OXFORD SOFTWARE ENGINEERING Software Engineering Services & Consultancy Slide 1.1© OSEL 2001 Software Project Management: MONITORING AND CONTROL SPIN - Agilent 5 April 2001

OXFORD SOFTWARE ENGINEERING Software Engineering Services & Consultancy Slide 1.2© OSEL 2001 Contents 1.Monitoring and control model 2.Activity data (monitoring) 3.Instructions (control) 4.Activity 5.Control

OXFORD SOFTWARE ENGINEERING Software Engineering Services & Consultancy Slide 1.3© OSEL 2001 ACTIVITY requirements & resources product

OXFORD SOFTWARE ENGINEERING Software Engineering Services & Consultancy Slide 1.4© OSEL 2001 ACTIVITY CONTROL requirements & resources product

OXFORD SOFTWARE ENGINEERING Software Engineering Services & Consultancy Slide 1.5© OSEL 2001 ACTIVITY CONTROL requirements & resources product activity data (monitoring)

OXFORD SOFTWARE ENGINEERING Software Engineering Services & Consultancy Slide 1.6© OSEL 2001 ACTIVITY CONTROL requirements & resources product activity data (monitoring) instructions (control)

OXFORD SOFTWARE ENGINEERING Software Engineering Services & Consultancy Slide 1.7© OSEL 2001 ACTIVITY CONTROL requirements & resources product activity data (monitoring) instructions (control) a feedback loop

OXFORD SOFTWARE ENGINEERING Software Engineering Services & Consultancy Slide 1.8© OSEL 2001 Monitoring and control is a feedback loop –it is not planning, estimating, progress reporting or the CMM L2 –most like (change control) 2 Examples of feedback loops / control mechanisms: –cistern and ball cock –governor on a steam engine Project feedback loop is not mechanical Many dimensions to control Heuristic not algorithmic –project - not production (but would like to be)

OXFORD SOFTWARE ENGINEERING Software Engineering Services & Consultancy Slide 1.9© OSEL 2001 There are defective feedback mechanisms (identify your favourite pathological projects)

OXFORD SOFTWARE ENGINEERING Software Engineering Services & Consultancy Slide 1.10© OSEL 2001 ACTIVITY CONTROL requirements & resources product instructions (control)

OXFORD SOFTWARE ENGINEERING Software Engineering Services & Consultancy Slide 1.11© OSEL 2001 ACTIVITY CONTROL requirements & resources product activity data (monitoring)

OXFORD SOFTWARE ENGINEERING Software Engineering Services & Consultancy Slide 1.12© OSEL 2001 ACTIVITY CONTROL requirements & resources product

OXFORD SOFTWARE ENGINEERING Software Engineering Services & Consultancy Slide 1.13© OSEL 2001 ACTIVITY CONTROL requirements & resources product activity data (monitoring)

OXFORD SOFTWARE ENGINEERING Software Engineering Services & Consultancy Slide 1.14© OSEL 2001 ACTIVITY CONTROL requirements & resources product activity data (monitoring) instructions (control) CONTROL

OXFORD SOFTWARE ENGINEERING Software Engineering Services & Consultancy Slide 1.15© OSEL 2001 ACTIVITY CONTROL requirements & resources product CONTROL

OXFORD SOFTWARE ENGINEERING Software Engineering Services & Consultancy Slide 1.16© OSEL 2001 requirements & resources product activity data (monitoring) instructions (control) CONTROL ACTIVITY

OXFORD SOFTWARE ENGINEERING Software Engineering Services & Consultancy Slide 1.17© OSEL 2001 It can be adapted to operate hierarchically (programme management) It can be adapted to operate with supply chains –but the nature of activity data and instructions information does change

OXFORD SOFTWARE ENGINEERING Software Engineering Services & Consultancy Slide 1.18© OSEL 2001 CONTROL modified activity data (monitoring) instructions (control) CONTROL

OXFORD SOFTWARE ENGINEERING Software Engineering Services & Consultancy Slide 1.19© OSEL 2001 ACTIVITY CONTROL instructions (control) What is this?

OXFORD SOFTWARE ENGINEERING Software Engineering Services & Consultancy Slide 1.20© OSEL 2001 Communication of activity data should be: –in place (available - now) –timely (real time) –simple –structured –complete –conventional (a standard to make life simple) –consistent because...

OXFORD SOFTWARE ENGINEERING Software Engineering Services & Consultancy Slide 1.21© OSEL 2001 Communication of activity data should typically describe : –work completed (and not completed) w.r.t. schedule –quality (usually unreported) –changes –risks –defects –actions and issues (what is an issue?) –others - e.g. resources, requirements in/satisfied, customer satisfaction…. individually and collectively –signal stress points and potential problems

OXFORD SOFTWARE ENGINEERING Software Engineering Services & Consultancy Slide 1.22© OSEL 2001 Example…..

OXFORD SOFTWARE ENGINEERING Software Engineering Services & Consultancy Slide 1.23© OSEL 2001 ACTIVITY CONTROL activity data (monitoring) What is this?

OXFORD SOFTWARE ENGINEERING Software Engineering Services & Consultancy Slide 1.24© OSEL 2001 Control instructions should be –accountable –informed by detailed activity data individual and collective for all indicators –justifiable - w.r.t. activity data –re-align control parameters Shown as decisions and change in emphasis in decisions in activity data –communicated (available now) –be well judged ! (heuristic not algorithmic)

OXFORD SOFTWARE ENGINEERING Software Engineering Services & Consultancy Slide 1.25© OSEL 2001 Example…..

OXFORD SOFTWARE ENGINEERING Software Engineering Services & Consultancy Slide 1.26© OSEL 2001 What is this ? CONTROL requirements & resources product activity data (monitoring) instructions (control)

OXFORD SOFTWARE ENGINEERING Software Engineering Services & Consultancy Slide 1.27© OSEL Do Work 2 Formal Technical Review (or test) 3 Store Work Products (library) reviewed work product rejected work (revise and re-eview)) CIs booked out for reference released product status reports Plans completed work product status reports and issues corrective action requests review records schedule change control to Track and Report Work PBSWBS product Copyright OSEL 1998

OXFORD SOFTWARE ENGINEERING Software Engineering Services & Consultancy Slide 1.28© OSEL 2001 ACTIVITY What is this? requirements & resources product activity data (monitoring) instructions (control)

OXFORD SOFTWARE ENGINEERING Software Engineering Services & Consultancy Slide 1.29© OSEL 2001 Copyright OSEL 1998

OXFORD SOFTWARE ENGINEERING Software Engineering Services & Consultancy Slide 1.30© OSEL 2001 O X F O R D S O F T W A R E E N G I N E E R I N G L I M I T E D 9 Spinners Court, 53 West End, Witney, Oxfordshire OX28 1NH Tel. +44 (0)