Click to add text SUITE SEM Implementation Process Training.

Slides:



Advertisements
Similar presentations
Page 2 Agenda Page 3 History –Blue Print, 2000 –GIS Process 1.2, 2001 (training only) –GIS Process 2.0, (ITIL based - not implemented) –Supply/Demand.
Advertisements

DataSource & SEI’s Capability Maturity Model (CMM ® )
CPIS 357 Software Quality & Testing I.Rehab Bahaaddin Ashary Faculty of Computing and Information Technology Information Systems Department Fall 2010.
A framework for describing IT Project Management Processes and Tool Set Features Enterprise Project Management Framework.
Improving Process for Better Software. Who We Are An experiential learning program that provides technology solutions for our partners, and real- world.
A GOAL-BASED FRAMEWORK FOR SOFTWARE MEASUREMENT
1 Samples The following slides are provided as samples and references for the Quarterly Reviews Additional slides will be added.
SUITE Systems Engineering Methodology (SEM)
Software Engineering For Beginners. General Information Lecturer, Patricia O’Byrne, office K115A. –
Click to add text SUITE SEM Implementation Awareness Presentation.
Pittsburgh, PA Software Engineering Institute Carnegie Mellon University Pittsburgh, PA Sponsored by the U.S. Department of Defense.
Project Management Methodology (PMM)
CMMI Overview Quality Frameworks.
The Software Product Life Cycle. Views of the Software Product Life Cycle  Management  Software engineering  Engineering design  Architectural design.
project management office(PMO)
Enterprise Architecture
SQA Work Procedures.
October 15, 2004 – 1 Welcome IPMA and SolutionsIQ Professional Event Testing, Testing, 1…2…3… Improving software quality -- one bug at a time.
What is Business Analysis Planning & Monitoring?
Chapter : Software Process
Complete and Integrated Lifecycle Management. Challenges 1.
The Software Development Life Cycle: An Overview
Project Management Process Overview
S T A M © 2000, KPA Ltd. Software Trouble Assessment Matrix Software Trouble Assessment Matrix *This presentation is extracted from SOFTWARE PROCESS QUALITY:
Software Engineering II Lecture 1 Fakhar Lodhi. Software Engineering - IEEE 1.The application of a systematic, disciplined, quantifiable approach to the.
Model-Based Process Improvement Module 2. Module Objectives This module will enable students to recall information about the history of CMMI fundamentals.
Riding the Web Tide A Practical Approach to Institutionalizing Project Management Riding the Web Tide A Practical Approach to Institutionalizing Project.
MSF Requirements Envisioning Phase Planning Phase.
Doing More with TeamTrack May 1, /17/2015 6:14 PM Goals and Objectives Increased Reuse of Critical Assets Increased Productivity and Effectiveness.
1 Chapter 2 The Process. 2 Process  What is it?  Who does it?  Why is it important?  What are the steps?  What is the work product?  How to ensure.
Introduction to Software Engineering LECTURE 2 By Umm-e-Laila 1Compiled by: Umm-e-Laila.
Presented by: Global Sage Group GSG Base Methodology Enrico Palumbo.
Chapter 2 Process: A Generic View
CSI - Introduction General Understanding. What is ITSM and what is its Value? ITSM is a set of specialized organizational capabilities for providing value.
December 14, 2011/Office of the NIH CIO Operational Analysis – What Does It Mean To The Project Manager? NIH Project Management Community of Excellence.
MD Digital Government Summit, June 26, Maryland Project Management Oversight & System Development Life Cycle (SDLC) Robert Krauss MD Digital Government.
IT Requirements Management Balancing Needs and Expectations.
Software Process Models
Lecture Topics covered CMMI- - Continuous model -Staged model PROCESS PATTERNS- -Generic Process pattern elements.
SWEN 5130 Requirements Engineering 1 Dr Jim Helm SWEN 5130 Requirements Engineering Requirements Management Under the CMM.
Process Improvement. It is not necessary to change. Survival is not mandatory. »W. Edwards Deming Both change and stability are fundamental to process.
Requirements Development in CMMI
CMMI FRAMEWORK SRIKANTH DEVINENI. Process failure is recognised when Project is delivered late Too much redundancy Customer complaints after delivery.
Cmpe 589 Spring 2006 Lecture 2. Software Engineering Definition –A strategy for producing high quality software.
Your Interactive Guide to the Digital World Discovering Computers 2012 Chapter 12 Exploring Information System Development.
6/6/ SOFTWARE LIFE CYCLE OVERVIEW Professor Ron Kenett Tel Aviv University School of Engineering.
Irish Institute of Training & Development JOHN SMITH & TREVOR DAGG.
Certification: CMMI Emerson Murphy-Hill. Capability Maturity Model Integration (CMMI) Creation of the Software Engineering Institute (SEI) at Carnegie.
Prof. Shrikant M. Harle.  The Project Life Cycle refers to a logical sequence of activities to accomplish the project’s goals or objectives.  Regardless.
1 Week 3 Software Engineering Spring Term 2016 Marymount University School of Business Administration Professor Suydam.
SQA project process standards IEEE software engineering standards
Project Planning: Scope and the Work Breakdown Structure
BIL 424 NETWORK ARCHITECTURE AND SERVICE PROVIDING.
School of Business Administration
CS4311 Spring 2011 Process Improvement Dr
SQA project process standards IEEE software engineering standards
Identify the Risk of Not Doing BA
CMMI Overview Quality Frameworks.
Select and Implement a Web Experience Management Solution
SUITE SEM Implementation Process Training
Hyper-V Cloud Proof of Concept Kickoff Meeting <Customer Name>
A possible solution: Personal Software Process (PSP)
CMMI – Staged Representation
ITSM Governance is Imperative to Succeed
Software Engineering I
Requirements Development in CMMI
Capability Maturity Model
Bridging the ITSM Information Gap
IT Next – Transformation Program
Presentation transcript:

Click to add text SUITE SEM Implementation Process Training

State of Michigan Department of Information Technology 2 From Vision to Action 2 Today’s Topics  SUITE Phase 1: Where We’ve Been  SUITE Phase 2: Where we are Now  Roll out of the process  Provide overall understanding of the SEM (Systems Engineering Methodology)  Detailed training as Applications are selected  SUITE Phase 3: Where We’re Going

State of Michigan Department of Information Technology 3 From Vision to Action 3 Communication & Training  TechTalk and Staff meetings  Awareness Presentations  Process Training  Detailed Template Training  Provided when needed  Assures standardized approach  Templates are easy to complete/modify!

State of Michigan Department of Information Technology 4 From Vision to Action 4 Useful Acronyms  SUITE = State Unified Information Technology Environment  SEM = Systems Engineering Methodology  CMMI = Capability Maturity Model Integrated  CMMI Level 3 = Maturity Level that is characterized by defined processes  SEI = Software Engineering Institute at Carnegie Mellon University  PMM= Project Management Methodology

State of Michigan Department of Information Technology 5 From Vision to Action 5 Long Range Vision: CMMI Level 3

State of Michigan Department of Information Technology 6 From Vision to Action 6 CMMI Benefits CMMI Provides: Guidance for efficient, effective improvement across multiple process disciplines in an organization  A common language and a shared vision  Collection of best practices  A way to define what improvement means for an organization  Roadmap for process improvement

State of Michigan Department of Information Technology 7 From Vision to Action 7 CMMI Performance Measures Based on SEI Research with 35 different organizations* Performance CategoryMedian Improvement Cost34% Schedule50% Productivity61% Quality48% Customer Satisfaction14% Return on Investment4:1 *Private Sector Experience

State of Michigan Department of Information Technology 8 From Vision to Action 8 Purpose of SUITE Provide an integrated CMMI Level 3 compliant systems development framework that encompasses:  Process Management  Project Management – Already rolled out  Systems Engineering  Support Processes

State of Michigan Department of Information Technology 9 From Vision to Action 9 Integration with Project Management Processes  What is a PMO  Single area  Matrixed  Developing  Coordination with Release Planning process  Release Schedules reflect SEM stages  Ability to validate SEM usage  Gather Process SEM metrics

State of Michigan Department of Information Technology 10 From Vision to Action 10 Useful SEM Terms  SEM – Systems Engineering Methodology  Stages and Stage Exits  Templates and Checklists  Process Guides  Touch Points  SEM Express  Inputs/Outputs – Items used and products developed

State of Michigan Department of Information Technology 11 From Vision to Action 11 Everyone needs to know the answer to four questions 1. What is SEM all about?  A standardized approach to development to assure we design, deliver and maintain applications that meet clients expectations  Michigan/1 for Application Development

State of Michigan Department of Information Technology 12 From Vision to Action 12 Everyone needs to know the answer to four questions 2. Why is MDIT doing it?  Develop more reliable, cost-effective, computer- based solutions while making efficient use of resources.  Improve coordination between functional areas across MDIT

State of Michigan Department of Information Technology 13 From Vision to Action 13 Everyone needs to know the answer to four questions 3. When will it happen  Wave one implementation begins in March

State of Michigan Department of Information Technology 14 From Vision to Action How will it affect me, my job, & my career?  Clients & managers will have better ways to manage and track projects.  Employees will have more standard ways to do their work.  More up-front effort results in higher quality delivered to production.  Increased interaction and coordination between DIT and agency staff will deliver solutions that meet client expectations.  Improved coordination will speed project implementation.

State of Michigan Department of Information Technology 16 From Vision to Action 16 Interaction with SEM

State of Michigan Department of Information Technology 17 From Vision to Action 17

State of Michigan Department of Information Technology 18 From Vision to Action 18 First Stage: Initiation and Planning  Description  Inputs  High Level Activities  TouchPoints  Outputs  Review Process  References  Bibliography Standard areas for each Stage

State of Michigan Department of Information Technology 19 From Vision to Action 19 Second Stage: Requirements Definition  Description  Inputs  High Level Activities  TouchPoints  Outputs  Review Process  References  Bibliography

State of Michigan Department of Information Technology 20 From Vision to Action 20 Requirements Stage Outputs Deliverables (Templates)  Requirements Specification Package  Requirements Traceability Matrix  Security Plan Updates  Maintenance Plan Updates  Software Configuration Management Plan Updates  Solution Assessment Completion  IS Services Request  Requirements Management Checklist

State of Michigan Department of Information Technology 21 From Vision to Action 21 Requirements Stage Outputs Requirements Specifications

State of Michigan Department of Information Technology 22 From Vision to Action 22 Requirements Stage Outputs Requirements Specifications Sample

State of Michigan Department of Information Technology 23 From Vision to Action 23 Requirements  Description  Inputs  High Level Activities  TouchPoints  Outputs  Review Process  References  Bibliography

State of Michigan Department of Information Technology 24 From Vision to Action 24 Requirements Stage Review Process Outputs  Structured Walkthrough  Formalized Peer Review  Walk through each requirement  Review for content, clarity and completeness  Stage Exit  Formal Signoff of Requirements Definition Stage  Involves both MDIT and Client Sponsors

State of Michigan Department of Information Technology 25 From Vision to Action 25 Requirement Stage Review Process Outputs Stage Exit Sample

State of Michigan Department of Information Technology 26 From Vision to Action 26 SEM Implementation Began March 2007

State of Michigan Department of Information Technology 27 From Vision to Action 27 Wave Strategy for Implementation  First Wave identifies at least one application or project per CSD  Waves 2 (using SEM Express) and 3 (using SEM Systems Maintenance Guide) add more applications until all areas are using the SEM  IO/Core Team –Local SEM Champion(s) to support the strategy

State of Michigan Department of Information Technology 28 From Vision to Action 28 How do I learn more?  TechTalk and Staff meetings  Awareness Presentations  Process Training  Detailed Template Training  As you implement where do you go for questions  Your Manager  Local IO Core team and SEM Champion(s)  Michigan.gov/SUITE

State of Michigan Department of Information Technology 29 From Vision to Action 29 How Can You Help  Embrace the Systems Engineering Methodology  Help identify areas to improve  Use this process to improve the quality of your work  Champion this process with the clients and others  Provide support to other staff and client as needed

State of Michigan Department of Information Technology 30 From Vision to Action 30 Today’s SUITE Process Training  Communication and Training  CMMI  Systems Engineering Methodology Approach  SEM Overview and Stages  Templates and Process Guides  Our implementation strategy  Where to go to find out more

State of Michigan Department of Information Technology 31 From Vision to Action 31 Questions ???

State of Michigan Department of Information Technology 32 From Vision to Action 32 Handouts?  Process Overview Chart  Template and completed template  Web Structure info – michigan.gov/suite  Touchpoint handout  Who is involved Communication matrix  Bring a SEM book as prop &/or for reveiw  presentations after session AND link