1 / 18

Better Systems? That means improvement of the development process!

Better Systems? That means improvement of the development process!. M.H.J. Vucsan 2005 Statistics Netherlands. Contents. The problem Strategy and methods RUP PRINCE II ISEB/TMAP Implementing Improvement From project to organisational goal. Context. Organizational change (2000). E.

marla
Download Presentation

Better Systems? That means improvement of the development process!

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. Better Systems? That means improvement of the development process! M.H.J. Vucsan 2005 Statistics Netherlands

  2. Contents • The problem • Strategy and methods • RUP • PRINCE II • ISEB/TMAP • Implementing Improvement • From project to organisational goal

  3. Context Organizational change (2000) E S output throughput input SUBJECT ORIENTED PROCESS ORIENTED

  4. The Problem • Stovepipes is partly culture • Desktop computing is less formal • Many kitchen table specialists • “Free” development is preferred mode • Real programmers don’t need methods • Rising level of complexity • Bigger applications thus bigger projects • Development process suboptimal • Not enough standards • Informal use of RAD (!!)

  5. Improvement projects • Projectmanagement • Development “soft side” project managers • Implementation of PRINCE II • Software development • Implementation of RUP • Software testing • Implementation of ISEB/TMAP • Selection based on market share and consultancy.

  6. Strategy (IT Division only) • Software aquisition • Rational suite for RUP • Courses • RUP training • PRINCE II/ Projectmanagement training • Coaching • Soft side project management • RUP process engineers • Testing

  7. The RUP Method • Based on UML modelling language • Fased, iterative development process • Interface behavour in Use-Cases • Specific roles for every activity • Specific process for every activity • Specific products for every activity • Lots of documents

  8. TMAP/ISEB method • Specified test process steps • Some standards like BS7925 • Specified test types • Components test, Systems test, Maintenance test etc. • Extensive body of knowledge of: • Test techniques; statement coverage, walkthroughs, statistical analysis, inspection etc.

  9. PRINCE II • Project management is management • Project environment • Project board • Project support • Stakeholders etc. • Business case is essential to a project • Risk containment • Fair amount of documents

  10. Directing a Project (DP) Controlling a Stage (CS) Starting Up (SU) Initiating a Project (IP) Managing Stage Boundaries (SB) Closing a Project (CP) Managing Product delivery (MP) Planning (PL) The PRINCE II™ processes

  11. Implementing Improvement First year • Testing and RUP OK • Project management too little benefits • Customer acceptation problems • Organisation not really project oriented • Increased formality causes acceptance problems

  12. Implementing improvement Second year • Programme scope change from IT-division into whole bureau. • Endorsed by the board of directors • Scope widening for RUP and testing • More people to be educated • Change of strategy for PRINCE II • Different implementation model

  13. Implementation PRINCE II • Workshops S3 top down • Flying Squad assists with method • Work group for guidance • Website with relevant information • Word templates • Presentations for all interested parties • IT projectmanagers strict reporting standards

  14. education Implementation model PRINCE II • TOP DOWN Top management Workers The workshops made the difference

  15. Teaching model PRINCE II Coaching thru participation modeling and support Coaching thru modeling and support S3 S2 low Relationship factor high Coaching thru leadership, facilitation, development mentoring and peer coaching Coaching thru direction and support S1 S4 low Task direction from coach high Hersey/Blanchard, Bolman/Deal

  16. From projects to organisational goal (April 2005) • Line management will be responsible for continuous improvement • IT division again focal point • Special interest groups to maintain knowledge • Measurement with OPM3 of maturity level of Project management (OPM3: Organisational Project Management Maturity Model) • to be repeated every half year

  17. OPM3 results 1/4/2005 Project management maturity level

  18. Thank You !!

More Related