1 Transdyne Corporation CMMI Implementations in Small & Medium Organizations Using the Agile Methodology to Mitigate the Risks of Highly Adaptive Projects Dana Roberson Quality Software Engineer NNSA Service Center And Dr. Mary Anne Herndon Transdyne Corporation SM CMM, CMMI, SCAMPI, SCAMPI Lead Assessor, SCAMPI Lead Appraiser, and SEI are service marks of Carnegie Mellon University. CMM and CMMI are registered in the U.S. Patent and Trademark Office by Carnegie Mellon University.
2 Agenda: Using the Agile Methodology to Mitigate the Risks of Highly Adaptive Projects Risks in Highly Adaptive Projects Typical Management Scenarios Agile CMMI Agile Software Development Methodology Steps for Implementing CMMI-DEV Practices in Agile Projects Strategy Map for Using Agile Practices Today Benefits Lessons Learned 2
3 Agile Methodology for Risk Management Transdyne Corporation CMMI Implementations in Small & Medium Organizations Dynamic Requirements Aggressive Schedule Limited Resources Using the Agile Methodology to Manage Risks of Highly Adaptive Projects Dynamic Requirements Aggressive Schedule Limited Resources Impact of customer co-location on requirements management & tasking Immediate effect of changing customer priorities & direction Typical work performed on a fixed LOE or time & material basis 3
4 Risks In Technology & Support Projects The requirements are ALWAYS changing. Time and schedules are ALWAYS aggressive. Resources will ALWAYS be tight. To mitigate these risks you need processes that address these risks to allow rapid adaptation.
5 Scenario for Risk Management Practices in Small Businesses Transdyne Corporation CMMI Implementations in Small & Medium Organizations Small businesses often function in focused markets as: Suppliers of specialized on-site technical services, key personnel, applications or products Domain specialists Staff augmentation These focused markets may not provide needed revenue or market share growth to readily prosper in today s economy. Costs of improving project and risk management practices are considered key investments in these vulnerable cash flow environments. Both near and long term cash flow analysis typically includes factors such as: Customer base stability & revenue cycles Projected revenue growth Costs of acquiring appropriate resources to improve management practices, such as training, process engineers and collaborative software and hardware. 5
6 Scenario for Implementing Risk Management Practices in Small Businesses (continued) Transdyne Corporation CMMI Implementations in Small & Medium Organizations $$$ Understanding and improving project management and risk management practices is a key factor in revenue growth. Planning improvements typically includes assessment of critical factors such as: Required resources (available staff, feasible schedule, platforms, facilities, collaborative tools) Past performance data (costs, schedules, lessons learned) Training in the domain and software development method (Agile) Risk identification and impact assessment Risk mitigation A practical knowledge base useful for improving management practices can be provided by process models, such as CMMI and ISO Obtaining CMMI benchmarks and ISO 9000 certifications are often stepping stones to expand government and commercial customers. Selecting and implementing any process and life cycle models is both costly and can be risky as there are no guarantees of success on-site with the customer. 6
7 Scenario for Implementing Risk Management in Small Medium Businesses (continued) Transdyne Corporation CMMI Implementations in Small & Medium Organizations Planning a process improvement strategy typically includes identifying problematic projects with typical issues such as: Limited resources and ambitious schedules Lack of experience and staff training Excessive staff turnover rate Stability of current customer base Projection of market growth Over commitment of key staff Inaccurate planning data for costs and schedule Implementing a process improvement strategy, small businesses should customize a path of small, adjustable steps. An example of a path of small steps is a hybrid approach of improving project and risk management practices in CMMI-DEV first. The next step is a selection of a life cycle model that is suitable for the work requirements, location and level of customer participation.
8 Building Bridges Using CMMI-DEV and Agile to Manage Risk Continuous Improvement Measurement & Analysis CMMI-DEV Resource Management Process Approach Customer Focused CMMI Is Designed to Be Tailored to Your Business Environment. Fully align process improvement with your business goals Look at what you are actually doing, If a good fit document and follow Leverage off existing activities e.g. Agile Promote maximum flexibility and efficiency in your process improvement approach Emphasize measurement and analysis Agile life cycle model 8
9 Key Process Improvement Factors & Sources of Risks All KEY process improvement factors introduce sources of risks to developers! Resources Training Business Case Contract Type Communication Life Cycle Models Project Planning Domain Experience Processes Choosing an incompatible life cycle development model impacts all other key process improvement factors.
10 Sources of Risks in Life Cycle Models spiral waterfall Waterfall cycle times impact of changing requirements direct end user involvement Spiral cycle times impact of changing requirements direct end user involvement Agile inadequate training customer awareness management advocacy 10
11 Practice Implementation Across Small Organizations Process Engineer Organization CMMI Process Management CMMI Engineering Framework of the CMMI-DEV model provides: 1. Increases in implementation efficiency due to redundancy in model functions, such as Project Management & Support Process Areas and generic practices. 2. Minimal opportunities for conflicts with customer, staff and resources with adequate model understanding CMMI Support CMMI Project Management 11 11
12 Steps for Implementing Risk Management with CMMI-DEV & Agile Understand the Risks Key growth Investments: Process & Agile training Collaborative H/W & S/W Process engineer support Lessons Learned What did we do well? Where were we lucky? What do we need to improve? Cost Schedule Technical Impact Metrics Status risks market area revenue/profit projected growth Identify risks: project specific technical impacts mitigation plans customer involvement High Medium Low Risk Template Develop Agile project plan Evaluate mitigation plans Evaluate business opportunity Risk of winning Contract type New customer Technical complexity Staff 12
13 Strategy Map for Implementing Risk Management Using Agile and CMMI-DEV Aggressive schedule Risk management tools Dynamic requirements Scrums Burn Down (MS Excel) Limited resources White Boards Peer Reviews Impromptu & Team Programming Agile Method Engineering Techniques CMMI-DEV Engineering Management Support Quality Assurance Configuration Management Measurement Structured Decisions 13 13
14 Risk Reduction Solution - Process Improvement Risk reduction is NOT fighting fires or just in time solutions. Reduce variation. Recognize and document best practices. It is simply a way of looking at how we can do our work better. A series of actions taken to identify, analyze and improve existing processes. These actions often follow a specific methodology or strategy to create successful results. Remove activities that have no value to the organization. Improve customer satisfaction. Process improvement is important as it has often been said that process accounts for 80% of all problems while people account for the remaining 20%. Provide lessons learned. Encourage staff members to contribute!
15 What are Best Practices and Benefits? Best practices are effective, high-leverage technical and management PROCESSES that have been implemented and proven on successful projects. Examples of Best Practices Proven Models i.e. CMMI-DEV, ISO 9001 Project Planning Measurement and Control Peer Reviews Risk Management Quality Assurance Status Reporting Benefits Risks are reduced & mitigated Repeatability is achieved Clarity and understanding are increased Common terminologies and consistent styles are developed and followed Configuration Management Agile Software Development
16 Typical Roadblocks and Hurdles to Process Improvement Resistance to Change Lack of Commitment and Resources We tried process improvement before, and it didn t buy us anything. CMMI /TQM/Agile/Lean Six Sigma/ and best practices are just another fad. Who s paying for it? If it isn t paid for, we re not doing it. I m retiring/transferring from this job soon, I don t have to get involved. Developers don t have the time because there is so much rework.
17 AGILE Software Development Methodology Activities are known as 'timeboxes. Each iteration passes through a full software development cycle, including: planning, requirements analysis, design, unit tests, Quality Assurance testing, coding until the unit tests pass and a working product is finally demonstrated to stakeholders. Documentation is no different than software design and coding for assuring repeatability and re-generation. Strong team discipline is required to code for agility. At the end of each iteration, stakeholders re-evaluate project priorities with a view to optimizing their return on investment. Agile emphasizes face to face communication with all stakeholders!
18 Agile Navigating Class IV Rapids (AKA Risk Reduction) CMMI-DEV CMMI-DEV provides process discipline Scrum enhances adaptability and commitment Agile Quality Product Agile means being able to quickly change direction Agile development methods minimize risk by developing software in multiple 'iterations' of short time frames Each iteration passes through a full software development cycle In our Agile projects, SCRUM Boards, Burndown charts and other project and working artifacts were defined and identified as CMMI artifacts. Face to face communication & EA reviews ensure peer review. At the end of each iteration, stakeholders reevaluate project priorities and risks.
19 Agilizing CMMI SCRUM and CMMI Incorporating CMMI Processes Tailoring processes to incorporate Agile iterations Mapping CMMI SPs to Agile iterations and artifacts Monitoring and controlling projects requirements and changes testing defects Using Agile at our shop Software Tools Visual Source Safe Configuration Management Source Control Visual Studio Development Environment SQL Management Studio Development environment Enterprise Architect Requirements management Requirements traceability Axosoft OnTime Defect Management Agile & CMMI-DEV Processes (Process Asset Library) Defined processes Scrums Scrum Boards Sprints Burn Down (MS Excel) White Boards Peer Reviews Team programming Performance metrics
20 Where to Start? Look at what you have in place What are you doing well - right now Establish your SEPG Tailor the CMMI process descriptions to map to current processes By-in by Software Engineering and Management PAL Develop processes for things you are not doing now Discuss with Software Engineering Team Train the Team! Follow up on how processes are being implemented and Modify if necessary to get a best fit!
21 Process Asset Library Processes and Standards
22 Process Descriptions Based on how We Do Business
23 Process Area Description Standards Developed by TWG within the SEPG available to all developers on SharePoint Site Work Environment Standards Web Design and Usability Guidelines Coding Standards
24 Development Initial Planning Cycle Project Backlog EA Management Tracked in EA through testing Process Descriptions Diagrams
25 Development Initial Planning Cycle Project Backlog EA Management Tracked in EA through testing Process Descriptions Mapping
26 Agile Focus on Quality Built-In Agile Resources to Develop Quality Products Sprint Plan Testing is built into each sprint Sprint Planning Requirements Available resources Development & QA Scrum Assign tasks to resources Reassign based on burndown Defect Workflow Maintenance resources QA assignment
27 class Scrum Process - Logical View Sprint Planning/Scrum Scrum Lifecycle (Iterative) Product Backlog Dependent On Sprint Planning Dependent On Sprint Planning/Plan Determine sprint timeline Determine available resources risks Scrum What done What Planned Obstacles - Risks Daily Scrum Meeting Updates Sprint Backlog Who, what, how Requirements Coding Testing Baselines Documentation Updates Scrum Board Dependent On Deliverable Demonstration to stake holders/ccb Deployment to User Acceptance Testing
28 Sprint Planning Sprint Planning/Plan Determine sprint timeline Determine available resources - Who, what how Requirements Coding Testing Baselines Documentation Deliverable Demonstration to stake holders/ccb Deployment to User Acceptance Testing
29 Design Process Project Plan Overall Design Sprint Planning Daily Scrum Developer review (Peer)
30 Gathering, Reviewing and Testing the Requirements Enterprise Architect Requirements Definition (Enterprise Architect) Requirements Review (EA export to web interface) Peer Review Developer review CCB review Requirements tied to activities and tests for traceability
31 Gathering and Managing Requirements - BA & QA
32 Requirements Management and Tracking SE and Customer
33 Coding/Unit Testing & Documentation Development Development of Functional unit on DEV environment Get latest of all code, unit test Check in Code to Visual Source Safe At prescribed interval, build full project, deploy to internal testing environment Automated Baseline Capture developed by team Well commented code Document changes to other developers code Context sensitive help in development environment and customer environment Notes and resolutions in Axosoft OnTime
34 Developer Interaction with QA reduces Risk Testing is built into the development cycle Early and frequent delivery ensures adequate time for feedback and reduces risk Agile benefits the IT department assisting in quicker better quality and reduced work Stressing repeatable processes for project management Internal Testing (DEV/QA) Developer notifies QA of functionality ready for testing Defect found by QA entered into Axosoft Ontime Developer fixes defect rebuilds- workflow in Ontime Ready for testing on TEST Defect Fixed or Failed Retest User Acceptance Testing (STAGE) Production (PROD)
35 Show screen from Axosoft
36 Acceptance Testing and Traceability
37 Monitoring and Controlling by Establishing Measurement Objectives MAP The NNSA SC ITD Apps Team maintains the Measurement and Analysis Plan (MAP). MAP defines the process performance measurement foundation established by applying the Goal Question Metrics (GQM) to the Applications Mission Statement The Apps Team leverages higher maturity level process performance management tools to: Build process performance databases using statistical process control (SPC). Track variance analyses (control charts with standard deviations) Analyze defects, accuracy of resource estimation, development and maintenance productivity and customer satisfaction
38 Measurement Objectives Low-cost of high-quality software applications and services, delivered rapidly, which supports high levels of customer satisfaction. (Mission Statement)
39 Monitoring and Controlling via Sprint Burndown Charts
40 Tracking Progress Across Sprints
41 Maintaining QA Assessments
42 Tracking Quality Corrective Actions
43 Lessons Learned in Managing Risks Using CMMI-DEV and Agile Transdyne Corporation CMMI Implementations in Small & Medium Organizations Management of complexity requires process discipline WHILE Management of change requires rapid adaptability. CMMI provides process discipline. SCRUM (Agile) enhances adaptability and commitment. 43
44 Lessons Learned in Managing Risks Using CMMI-DEV and Agile Transdyne Corporation CMMI Implementations in Small & Medium Organizations Understand that all process improvement opportunities, as with all investments, have costs and risks. Introducing Agile, as with any new technology, needs the advocacy of all project stakeholders. Participation of key staff members in planning practice implementation is needed to understand the continuity and costs and identify the key risks, such as customer culture. The CMMI Risk Management Process Area practices are easily tailored and implemented via a suitable template for Agile based projects. The Agile method emphasizes on-going requirements & design verification, daily SCRUMS with customer participation and team espirit de corp. The Agile emphasis on these activities provides engineering practices that reduce risks in software engineering tasks. 44
45 Remember CMMI-DEV is a process model, NOT a process description. CMMI-DEV only defines WHAT to do, not HOW to do it. Plan the process implementation so that you are taking advantage of the CMMI-DEV practices AND Use the Agile Methodology for rapid turn around for low cost quality product.
46 The End Transdyne Corporation CMMI Implementations in Small & Medium Organizations You have just seen key benefits of using CMMI-DEV and Agile to reduce risks in software engineering from the 30,000 feet level. Questions or Comments? 46
47 Examples of Mapped CMMI Specific Practices to Agile Life Cycle Steps
Leveraging CMMI framework for Engineering Services Regu Ayyaswamy, Mala Murugappan Tata Consultancy Services Ltd. Introduction In response to Global market demand, several OEMs adopt Global Engineering
Distributed and Outsourced Software Engineering The CMMI Model Peter Kolb Software Engineering SEI Trademarks and Service Marks SM CMM Integration SCAMPI are service marks of Carnegie Mellon University
www.businessbeam.com CMMI for Development Introduction & Implementation Roadmap Business Beam (Pvt.) Limited Today 1 About CMMI for Development 2 Implementation Roadmap 3 CMMI & Business Beam 2 About CMMI
Process Methodology for Wegmans Deli Kiosk Version 1.0 Prepared by DELI-cious Developers Rochester Institute of Technology September 15, 2013 1 Table of Contents 1. Process... 3 1.1 Choice... 3 1.2 Description...
& CMMI July, 2007 Why the drive for CMMI? Missed commitments Spiralling costs Late delivery to the market Last minute crunches Inadequate management visibility Too many surprises Quality problems Customer
Reaching CMM Levels 2 and 3 with the Rational Unified Process Rational Software White Paper TP174 Table of Contents INTRODUCTION... 1 LEVEL-2, REPEATABLE... 3 Requirements Management... 3 Software Project
Scrum and CMMI Level 5: The Magic Potion for Code Warriors Jeff Sutherland, Ph.D. Patientkeeper Inc. firstname.lastname@example.org Carsten Ruseng Jakobsen Systematic Software Engineering email@example.com
Using Organizational Business Objectives to Guide a Process Improvement Program Software Engineering Institute Carnegie Mellon University Pittsburgh, PA 15213 (SEI) SEPG North America March 2011 Agenda
Software Development Life Cycle (SDLC) and Development Methods There are some enterprises in which a careful disorderliness is the true method. Herman Melville Capability Maturity Model (CMM) A Capability
Applying CMMI SM In Information Technology Organizations Mark Servello, Vice President Jim Gibson, Senior Consultant ChangeBridge, Incorporated Page 1 Portions Copyright 2002 Carnegie Mellon University
Software Development Life Cycle (SDLC) Supriyo Bhattacharjee MOF Capability Maturity Model (CMM) A bench-mark for measuring the maturity of an organization s software process CMM defines 5 levels of process
Future of CMM and Quality Improvement Roy Ko Hong Kong Productivity Council 1 Agenda Future Development of CMMI CMMI and Small Organizations CMMI and Agile Development Good Enough Quality CMMI and Other
Certified Software Quality Engineer (CSQE) Body of Knowledge The topics in this Body of Knowledge include additional detail in the form of subtext explanations and the cognitive level at which the questions
IBM Software Group Requirement Management with the Rational Unified Process RUP practices to support Business Analyst s activities and links with BABoK Jean-Louis Maréchaux Software IT Specialist IBM Rational
Aligning CMMI & ITIL Where Am I and Which Way Do I Go? 2006 - cognence, inc. Agenda Where Am I? Current Situation Process Improvement Objectives How Do I Get There? CMMI ITIL Mapping, Commonalities, Differences
NEOXEN MODUS METHODOLOGY RELEASE 18.104.22.168 INTRODUCTION TO QA & SOFTWARE TESTING GUIDE D O C U M E N T A T I O N L I C E N S E This documentation, as well as the software described in it, is furnished under
Demand & Requirements Management Software Development QA & Test Management IT Operations & DevOps Change Management Agile, SAFe, Waterfall Support Overview codebeamer is a single-repository Application
SW Process Improvement and CMMI Dr. Kanchit Malaivongs Authorized SCAMPI Lead Appraisor Authorized CMMI Instructor Topics of Presentation Why improvement? What is CMMI? Process Areas and Practices in CMMI
What is a life cycle model? Framework under which a software product is going to be developed. Defines the phases that the product under development will go through. Identifies activities involved in each
TeamCompanion Solution Overview Visual Studio Information in this document, including URL and other Internet Web site references, is subject to change without notice. Unless otherwise noted, the example
Developing CMMI in IT Projects with Considering other Development Models Anahita Ahmadi* MSc in Socio Economic Systems Engineering Organizational Process Development Engineer, International Systems Engineering
When is Agile the Best Project Management Method? Lana Tylka Staged Incremental Deliveries Prototypes Plan Develop Design Deploy Test Maintain Sequential Steps Multiple Iterations Waterfall Sprints, Spirals
The Compelling Case For CMMI-SVC: CMMI-SVC, ITIL & ISO20000 demystified T: 01748 821824 E: firstname.lastname@example.org Agenda What is CMMI-SVC? How Does CMMI-SVC Relate to Existing Models? CMMI-SVC and ISO 20000
Software Development Process A software development process, also known as software development lifecycle, is a structure imposed on the development of a software product. Similar terms include software
Quality Assurance in an Agile Environment 1 Discussion Topic The Agile Movement Transition of QA practice and methods to Agile from Traditional Scrum and QA Recap Open Discussion www.emids.com 2 What is
SEI Level 2, 3, 4, & 5 1 Work Breakdown Structure (WBS) 1.0 SEI Product 1.1 SEI Level 2 Product 1.1.1 SEI Level 2 Process 22.214.171.124 Requirements Management Process 126.96.36.199 Software Project Planning Process
MM Agile: SCRUM + Automotive SPICE Electronics Infotainment & Telematics 20 Novembre, 2010 INDEX Introduction Why MM Agile Approach? How did we align classical and agile approach? How do we implement SCRUM?
www.ijcsi.org 160 Towards a new approach of continuous process improvement based on CMMI and PMBOK Yassine Rdiouat 1, Naima Nakabi 2, Khadija Kahtani 3 and Alami Semma 4 1 Department of Mathematics and
Realizing CMMI using Enterprise Architect and UML for Process Improvement Jack Hunnicutt, Anteon Corporation www.anteon.com Ramsay Millar, integrate IT architects LLC www.integrateitarchitects.com Introduction
Leveraging Agile and CMMI for better Business Benefits Presented at HYDSPIN Mid-year Conference 2014 28-Jun-2014 Outline 2 Context Key Business Imperatives Agile Adoption and CMMI Roadmap CMMI+Agile Best
Copyright Rational Software 2003 http://www.therationaledge.com/content/jan_03/f_cmmi_rr.jsp Using Rational Software Solutions to Achieve CMMI Level 2 by Rolf W. Reitzig Founder, Cognence, Inc. Over the
CENTRE (Common Enterprise Resource) Systems and Software Engineering Platform designed for CMMI compliance Capability Maturity Model Integration (CMMI) is a process improvement approach that provides organizations
Plan-Driven Methodologies The traditional way to develop software Based on system engineering and quality disciplines (process improvement) Standards developed from DoD & industry to make process fit a
White Paper IT Methodology Overview & Context IT Methodologies - Delivery Models From the inception of Information Technology (IT), organizations and people have been on a constant quest to optimize the
Match point: Who will win the game, ITIL or CMMI-SVC? NA SEPG 2011 Paper Presentation Anju Saxena John Maher IT Process and Service Management Global Consulting Practice ITIL is a Registered Trade Mark,
R Integrating CMMI, TSP and Change Management Principles to Accelerate Process Improvement SM Julie Switzer, P-3 Process Improvement Lead, NAVAIR Orville Starnes, TSP Launch Coach, NAVAIR R CMM, CMMI and
CON ECT INFORMUNITY, 19.9.2013 Neue Software-Trends Agilität Prozesse & RE Agile SW Development @ Siemens Corporate Development Center Dr. Kurt Hofmann > 25 years Siemens ACT SW developer at PSE Team leader
Cost effective methods of test environment management Prabhu Meruga Director - Solution Engineering 16 th July SCQAA Irvine, CA 2013 Agenda Basic complexity Dynamic needs for test environments Traditional
Introduction In today's world, software is becoming a larger part of many products and services. As the importance of software in systems increases, they are strongly influenced by software quality and
Pittsburgh, PA 15213-3890 Capability Maturity Model Integration ( ) Overview SM CMM Integration, SCAMPI, SCAMPI Lead Appraiser, and SEI are service marks of Carnegie Mellon University., Capability Maturity
Interpreting Capability Maturity Model Integration (CMMI ) for Service Organizations a Systems Engineering and Integration Services Example Mary Anne Herndon, SAIC Robert Moore, SAIC Mike Phillips, Software
Scrum and CMMI: A High level assessment of compatibility Srinivas Chillara 1 and Pete Deemer 2 Abstract: This article s purpose is to assess the compatibility of Scrum with CMMI and also provide a base
0305203 0305280 0305301 0305302 Software Engineering/Courses Description Introduction to Software Engineering Prerequisite: 0306211(Computer Programming 2). This course introduces students to the problems
CMMI LUXOFT ADVANTAGES International Quality Standards CMMI CIS s first SEI CMM/CMMI level 5 assessment in 2003, Europe s first SEI CMMI v1.2 Level 5 assessment in 2007 ISO annual confirmation of ISO 9001:2008
YOUR SUCCESS IS OUR FOCUS Whitepaper Published on: Jun-09 Author: Ramesh & Lakshmi Narasimhan 2009 Hexaware Technologies. All rights reserved. Table of Contents 1. Introduction 2. Subject Clarity 3. Agile
Enhancing The ALM Experience Tools to Accelerate Delivery of Secure, Reliable Modern Applications Brent Dorenkamp Solutions Architect Agenda Application Modernization and the Instant-On Enterprise Building
Life Cycle Models, CMMI, Lean, Six Sigma Why use them? John Walz IEEE Computer Society, VP for Standards QuEST Forum Best Practices Conference Track 3 What, Where, How & Why Monday, 24-Sep-07, 4:30 5:30
Basic Unified Process: A Process for Small and Agile Projects Ricardo Balduino - Rational Unified Process Content Developer, IBM Introduction Small projects have different process needs than larger projects.
Process Improvement From the Software Engineering Institute: The Software Capability Maturity Model (SW-CMM, CMMI) (Especially CMMI V1.1 Tutorial) The Personal Software Process (PSP) (Also see The Team
Audit Checklist The following provides a detailed checklist to assist the audit team in reviewing the health of a project. Relevance (at this time) How relevant is this attribute to this project or audit?
Outsourc es erv ice Engagement Domain Experts Vendor Account er d i ov Pr Finance Executive Sponsor Bo sto n C h ic a g o Project Empowering Agile with PPM Digite, Inc. 21060 Homestead Rd, Suite 220, Cupertino,
Overview The Business Analysis Capabilities Assessment is a framework for evaluating the current state of an organization s ability to execute a business automation effort from and end-to-end perspective..
EMC PERSPECTIVE Adopting an Agile Approach to OSS/BSS Development Reader ROI The agile software methodology is different from the traditional approach in that requirements gathering and analysis, design,
JOB DESCRIPTION APPLICATION LEAD The Application Lead will provide functional support and to expand capabilities in the area of systems configuration. This function provides the initial step in the process
Sprint with Scrum and get the work done Kiran Honavalli, Manager Deloitte Consulting LLP March 2011 Contents About Deloitte Consulting 3 Executive summary 4 About Scrum 5 Scrum phases 8 Lessons learned
A Report on The Capability Maturity Model Hakan Bayraksan hxb07u 29 November 2009 G53QAT Table of Contents Introduction...2 The evolution of CMMI...3 CMM... 3 CMMI... 3 The definition of CMMI... 4 Level
RUP for Software Development Projects George Merguerian www.bmc-online.com 1 Specialists in Global Project Management Brussels Frankfurt Houston Istanbul Milan Ottawa Shanghai Singapore Warsaw Washington
Metrics for the transformational age Essential Metrics for Agile Project Management Alex Birke, Agile World 2015 Accenture, its logo, and 'High Performance. Delivered.' are trademarks of Accenture. Why
Enabling Continuous Delivery by Leveraging the Deployment Pipeline Jason Carter Principal (972) 689-6402 Jason.email@example.com Pariveda Solutions, Inc. Dallas,TX Table of Contents Matching
Global trends in Process improvement SEPG North America, Oct 2013 Agenda Changing business environment Top 7 trends in Process improvement Case Studies Summary 2 The Business environment around us is changing
Capstone Agile Model (CAM) Capstone Agile Model (CAM) Approach Everything we do within the Capstone Agile Model promotes a disciplined project leadership process that encourages frequent inspection and
Water-Scrum-Fall Agile Reality for Large Organisations By Manav Mehan Principal Agile consultant Manav.Mehan@tcs.com Interests and Experience Leading Change and Transformation in Large, Complex organisations
Overview This is a 15-day live facilitator-led or virtual workshop is designed to prompt your entire team to work efficiently with Microsoft s Application Lifecycle Management solution based around Visual
How do you manage the growing complexity of software development? Is your software development organization as responsive to your business needs as it could be? Borland Core SDP enables your IT organization
Project Management and Scrum A Side by Side Comparison by Anne Loeser, October 2006 For decades, software development projects have followed the classic waterfall method in which software development initiatives
Requirements Engineering in Healthcare: Challenges, Solution Approaches and Best Practices MedConf 2009 Munich, October 13-15,2009 Table of Contents Siemens Healthcare and Vector Consulting Services Motivation
The document in this file is adapted from the IEEE standards for Software Project Management Plans, 1058-1998, which conforms to the requirements of ISO standard 12207 Software Life Cycle Processes. Tailor
NEOXEN MODUS METHODOLOGY RELEASE 188.8.131.52 INTRODUCTION TO PROJECT MANAGEMENT GUIDE D O C U M E N T A T I O N L I C E N S E This documentation, as well as the software described in it, is furnished under
CMMI KEY PROCESS AREAS http://www.tutorialspoint.com/cmmi/cmmi-process-areas.htm Copyright tutorialspoint.com A Process Area is a cluster of related practices in an area that, when implemented collectively,
A Viable Systems Engineering Approach Presented by: Dick Carlson (firstname.lastname@example.org) Philip Matuzic (email@example.com) i i Introduction This presentation ti addresses systems engineering
wibas Team Agile Process Improvement Sprint Change Method Leading Change. Sharing Knowledge. For internal use only -1- Seen this? For internal use only -2- Many change projects still spent most of their
Comparing Scrum And CMMI How Can They Work Together Neil Potter The Process Group firstname.lastname@example.org 1 Agenda Definition of Scrum Agile Principles Definition of CMMI Similarities and Differences CMMI
Preface Acknowledgements xi xiii 1. Introduction and Overview 1 Introduction 1 Whatis the CMMI"? 2 What the CMMI* is Not 3 What are Standards? 3 2. Summaryof CMMI-SW 5 The CMM*-SW 5 CMMI--SW Continuous
Manage the acquisition of products from suppliers for which there exists a formal agreement. Establish Supplier Agreements (SG 1) Supplier Requirements Supplier Agreements s Satisfy Supplier Agreements
2015 IBM Continuous Engineering Open Labs Target to better LEARNING (NO COST - not a substitute for full training courses) Choose from one or more of these Self-Paced, Hands-On Labs: DMT 3722 - Learn to
CASE STUDY ORACLE NAIO Excellence combined with Quality A CMMI Case study softwaredi xide com www.qaiasia.com THE CLIENT Process and Quality are important for measuring improvement. Improvement means different
IT service management is often equated with the Information Technology Infrastructure Library (ITIL), even though there are a variety of standards and frameworks contributing to the overall ITSM discipline.
The Application of IEEE Software and System Engineering Standards in Support of Software Process Improvement Susan K. (Kathy) Land Northrop Grumman IT Huntsville, AL email@example.com In Other Words Using
Truly Managing a Project and Keeping Sane While Wrestling Elegantly With PMBOK, Scrum and CMMI (Together or Any Combination) Neil Potter The Process Group Lead Appraiser / Improvement Coach Organization
Draft Documents RFP 3.2.4 In accordance with RFP 3.2.4, CNSI includes the required draft documents in the following order: Work Plan: Team CNSI provides a comprehensive draft Work Plan for the Iowa EHR
Capability Maturity Model Integration (CMMI ) Version 1.2 Overview SM CMM Integration, IDEAL, Personal Software Process, PSP, SCAMPI, SCAMPI Lead Appraiser, Team Software Process, and TSP are service marks
PMP Examination Tasks Puzzle game Here is a great game to play to test your knowledge of the tasks you will be tested on in the actual examination. What we have done is take each of the domain tasks in
Are waterfall and agile project management techniques mutually exclusive? by Eve Mitchell, PwC 22 MARCH 2012 www.pmtoday.co.uk Projects need to be managed to be successful Change is a ubiquitous feature