We think you have liked this presentation. If you wish to download it, please recommend it to your friends in any social system. Share buttons are a little bit lower. Thank you!
Presentation is loading. Please wait.
Published byNathan Grimshaw
Modified about 1 year ago
© 2013 IBM Corporation Tivoli and Maximo Quality Improvement Initiatives March 2014
© 2013 IBM Corporation Maximo / IBM Focus on Quality Prior to 2006, Maximo built on MRO’s tradition of quality Focus on Customers, Partnerships, Scenarios Iterative Software Development Lifecycle General processes in Design, Coding, Testing, Documentation Enhancements from IBM Phase based periodic checkpoints (Decision Check Points) Formal Councils and Reviews (Quality) Best Practices: –Agile development methodologies –“Shift Left” –Test automation –Defect causal analysis Result: Comprehensive, client focused Quality Management Program Corporate quality model at all levels of the organization Integration between business, development, and quality processes
© 2013 IBM Corporation Page 3 Documented IBM-wide Policies Corporate Quality Policy –Quality is recognized as a fundamental component of the value customers receive Corporate Instruction Continuous Quality Improvement (ET 105) Corporate Instruction Continuous Quality Improvement All deliverables will set aggressive quality improvement targets better than the predecessor product release All product quality plans must address: –In-Process Quality Predictive Indicators (QPIs) measure and monitor product quality through the development cycle –A formal fact-based Quality Certification prior to product release –Post release goals for all problem reports reflect improvement of previous releases –Post release measurements and reporting to validate goals or plans established to address issues Quality goals must be assessed throughout the overall offering lifecycle. Documented IBM Policies
© 2013 IBM Corporation Integrated Process for Continuous Quality Improvement Agile and Quality Best Practices Stakeholder feedback, Shift Left, UT, Automation Customer and Field driven improvements Customer Environments and Scenarios, Escape analysis Think 40 – Continuous Skills Development Top Development, Security, Quality and Process skills
© 2013 IBM Corporation Driving Continuous Quality Improvement Quality Checkpoints (Plan, Risk, Cert, and Post-GA) Drives Continuous Quality Improvement from release to release. Sets targets, and tracks results and actions for: Quality Predictive Indicators (QPIs), Field Quality (APARs and PMRs) Key Initiatives: Consumability, Security, Serviceability.. “Quality Champions” program Trained Leaders supporting targets, training, and teams Review Quarterly divisional compliance and Quality targets Guides teams through Quality Checkpoint process Senior Development management Establishes specific and appropriate, division-level quality goals Reviews and Approves Quality plans and certifications, as applicable Reviews applicable measurements and initiates necessary corrective actions
© 2013 IBM Corporation The Tivoli Agile Development Model Maximo utilizes Agile development best practices referenced in the “Tivoli Agile Development Model”. Agile: Uses continuous stakeholder feedback to deliver high-quality, consumable code through user stories and a series of short, stable, time-boxed iterations. Each sprint is time-boxed Earliest sprints address greatest risks. Smaller pieces delivered frequently. Stakeholder feedback guides development Requirements Stakeholder Review/Input Client Experience
© 2013 IBM Corporation Maximo Standard Operating Procedures Library of Maximo procedures used to deliver high quality products with in the IBM SWG system. Examples include: AM020 - Software Development Life Cycle Guidelines AM040 - Third Party Software Supplier Selection and Management AM050 - Software Release Information DOC010 - Information Development Procedures DP071 - Software Source Control Procedure DP072 - Maximo Build Procedure DP073 - Unit Testing QA030 - Quality Assurance Test Procedure QA040 - Quality Criteria QA090 - Quality Assurance Automation Testing QM010 - Maximo Code Review Procedure QM010 - Maximo Formal Code Inspection Procedure
© 2013 IBM Corporation Summary Maximo’s strong tradition in customer partnerships and quality completely align with IBM SWG’s Quality Management System The Maximo solution leverage an integrated management system driving continuous improvement targets and actions, with the right skills and best practices, and strong executive support. Results: in improved customer experience and field quality.
Software Quality Assurance Plan. The plan provides the guidelines for development of software to ensure the quality required in a software project These.
Copyright 2015, Robert W. Hasker. Classic Model Gathering Requirements Specification Scenarios Sequences Design Architecture Class, state models Implementation.
Current Trends in Systems Develpment Satzinger, Jackson, and Burd Object-Orieneted Analsys & Design Chapter 14.
Challenges in Agile Unclear project scope, multiple iterations, minimal documentation, early and frequent testing needs and active stakeholder involvement.
Agile Development Implementation Considerations. Agile software development is a methodology based on iterative and incremental development, where requirements.
Iterative development and The Unified process Chapter 2 Applying UML and Patterns -Craig Larman.
QuEdge Testing Process Delivering Global Solutions.
CUNA Mutual Group’s Quality Assurance Process In the context of Solution Delivery.
Cybersecurity: Engineering a Secure Information Technology Organization, 1st Edition Chapter 7 Software Supporting Processes and Software Reuse.
-Nikhil Bhatia 28 th October What is RUP? Central Elements of RUP Project Lifecycle Phases Six Engineering Disciplines Three Supporting Disciplines.
S/W Project Management Software Project Planning.
WEEK SEVEN AWARENESS & TRAINING COMMUNICATION & COORDINATION ADMS 3703.
Overview of RUP Lunch and Learn. Overview of RUP © 2008 Cardinal Solutions Group 2 Welcome Introductions What is your experience with RUP What is.
Evaluate Phase Pertemuan Matakuliah: A0774/Information Technology Capital Budgeting Tahun: 2009.
Industrial Software Project Management Some views on project managing industrial and business software projects.
IT Services SDLC, Peer and Gate Review Approach September 2011.
SAP Methods Context PRM1_02.1 PwC Methods & Risk Management Lesson Objectives Participants will be able to: Understand how methods can mitigate project.
> Blueprint Kickoff >. Introductions Customer Vision & Success Criteria Apigee Accelerator Overview Blueprint Schedule Roles & Responsibilities Communications.
© 2007 BigVisible Solutions, Inc. All Rights Reserved Training Solutions Agile Training Game v
The Integration Story: Rational Quality Manager / Team Foundation Server / Quality Center.
Search Engine Optimization © HiTech Institute. All rights reserved. Slide 1 What is Business Analysis Planning & Monitoring?
Project Management Project Integration Management Minder Chen, Ph.D. CSU Channel Islands
1 Chapter 4 An Agile View of Process. 2 The Manifesto for Agile Software Development “We are uncovering better ways of developing software by doing it.
Info-Tech Research Group1 Manage the IT Portfolio World Class Operations - Impact Workshop.
PRJ566 Project Planning & Management Software Architecture.
Info-Tech Research Group1 Info-Tech Research Group, Inc. Is a global leader in providing IT research and advice. Info-Tech’s products and services combine.
9/7/20151 Compiled by Arthur Alexander Reyes. Introduction to Software Quality Assurance (SQA)
Demystifying the Business Analysis Body of Knowledge Central Iowa IIBA Chapter December 7, 2005.
1 Project Management C53PM Session 3 Russell Taylor Staff Work-base – 1 st Floor
1 © Quality House QUALITY HOUSE The best testing partner in Bulgaria.
Chapter 4 Agile Development 1. The Manifesto for Agile Software Development 2 “We are uncovering better ways of developing software by doing it and helping.
A Prototyping Lifecycle. The Waterefall Model and Prototyping 4 As early as the 1980’s the classic “Waterfall model” of software development was criticised.
CLEANROOM SOFTWARE ENGINEERING. Cleanroom Software Engineering Cleanroom Software Engineering Process Lifecycle Process Lifecycle The Processes.
Chapter 3 Agile Development 1. What is “Agility”? Effective (rapid and adaptive) response to change Effective communication among all stakeholders.
Software Engineering Process - II 7.1 Unit 7: Quality Management Software Engineering Process - II.
by: Er. Manu Bansal Deptt of IT Software Quality Assurance.
Quality Activity Matrix Presented by Sandra Toalston President, SanSeek 1.
SOFTWARE DEVELOPMENT PROCESS PRACTICAL ASPECTS Information Software Systems ISS Modern SW Development Practices: Processes and Technologies 18 May 2007.
What’s New in SPEED APPS 2.3 ? Business Excellence Application Services.
PROJECT TITLE Project Leader: Team: Executive Project Sponsor (As Required): Date: Month/Day/Year 110/17/2014 V1.
How To Build a Testing Project 1 Onyx Gabriel Rodriguez.
Software Engineering (CSI 321) Software Process: A Generic View 1.
The Relationship between Cost & Quality Submitted by: Haya A. El-Agha Submitted to: Eng. Hani Abu Amr.
Quality Management How To Apply Quality Management alphaPM Inc.
+ Agile Usability Testing Methods Glenn Teneycke.
Info-Tech Research Group1 Requirements Gathering World Class Operations - Impact Workshop.
CEN rd Lecture CEN 4021 Software Engineering II Instructor: Masoud Sadjadi Phases of Software.
Fifth Lecture Hour 9:30 – 10:20 am, September 9, 2001 Framework for a Software Management Process – Life Cycle Phases (Part II, Chapter 5 of Royce’ book)
W5HH Principle As applied to Software Projects Compiled by Dr. Peri Sastry.
© 2017 SlidePlayer.com Inc. All rights reserved.