Www.methoda.com MethodAssess System Assessment. Methoda Computers Ltd 2 List of Subjects 1. Introduction 2. Actions and deliverables 3. Lessons and decisions.

Slides:



Advertisements
Similar presentations
System Development Life Cycle (SDLC)
Advertisements

Chapter 7: Key Process Areas for Level 2: Repeatable - Arvind Kabir Yateesh.
Chapter 3 Project Initiation
ClosingExecuting/ Controlling ControllingPlanningInitiatingOpportunityAssessment Client AcceptancePlanning ApprovalInitiating ApprovalOpportunity Assessment.
Effective Project Management: Traditional, Agile, Extreme
Project Integration Management Sections of this presentation were adapted from A Guide to the Project Management Body of Knowledge 4 th Edition, Project.
R R R CSE870: Advanced Software Engineering (Cheng): Intro to Software Engineering1 Advanced Software Engineering Dr. Cheng Overview of Software Engineering.
Project Work and Administration
Pertemuan Matakuliah: A0214/Audit Sistem Informasi Tahun: 2007.
By Saurabh Sardesai October 2014.
ECM Project Roles and Responsibilities
4 4 By: A. Shukr, M. Alnouri. Many new project managers have trouble looking at the “big picture” and want to focus on too many details. Project managers.
The Agile vs. Waterfall Methodologies Systems Development:  the activity of creating new or modifying / enhancing existing business systems.  Objectives.
Welcome to CMPE003 Personal Computer Concepts: Hardware and Software Winter 2003 UC Santa Cruz Instructor: Guy Cox.
© 2008 Prentice Hall11-1 Introduction to Project Management Chapter 11 Managing Project Execution Information Systems Project Management: A Process and.
Project Execution.
Project Life Cycle Introduction and Overview © Ed Green Penn State University All Rights Reserved.
Project Management Fundamentals Project Organization and Integration
Systems Analysis and Design: The Big Picture
MethodECMS © כל הזכויות שמורות. Methoda Computers Ltd 2 MethodECMS  MethodECMS is a proactive package that enables the establishment.
Project Management Process Overview
System design technique  System Development Life Cycle  Prototyping  Rapid Application Development.
CHAPTER 5 Infrastructure Components PART I. 2 ESGD5125 SEM II 2009/2010 Dr. Samy Abu Naser 2 Learning Objectives: To discuss: The need for SQA procedures.
SQA Architecture Software Quality By: MSMZ.
PMP® Exam Preparation Course
9 Closing the Project Teaching Strategies
Chapter 4 Components of the Software Quality Assurance System
MethodQMS Quality Management System.
Module CC3002 Post Implementation Issues Lecture for Week 1 AY 2013 Spring.
Demystifying the Business Analysis Body of Knowledge Central Iowa IIBA Chapter December 7, 2005.
Chapter 13: Developing and Implementing Effective Accounting Information Systems
© 2015 Cengage Learning. All Rights Reserved. May not be scanned, copied or duplicated, or posted to a publicly accessible website, in whole or in part.
EARTO – working group on quality issues – 2 nd session Anneli Karttunen, Quality Manager VTT Technical Research Centre of Finland This presentation.
Centro de Estudos e Sistemas Avançados do Recife PMBOK - Chapter 4 Project Integration Management.
1.  Describe an overall framework for project integration management ◦ RelatIion to the other project management knowledge areas and the project life.
Lecture 11 Managing Project Execution. Project Execution The phase of a project in which work towards direct achievement of the project’s objectives and.
Effective Project Management: Traditional, Agile, Extreme Presented by (facilitator name) Managing Complexity in the Face of Uncertainty Ch08: How to Close.
Project monitoring and Control
© 2012 Cengage Learning. All Rights Reserved. This edition is intended for use outside of the U.S. only, with content that may be different from the U.S.
Georgia Institute of Technology CS 4320 Fall 2003.
Systems Analysis and Design
Project Kick-off Meeting Presented By: > > > > Office of the Chief Information Officer.
INFORMATION SYSTEMS FOR MANAGEMENT. Agenda Information system project Organization analysis.
1 TenStep Project Management Process ™ PM00.9 PM00.9 Project Management Preparation for Success * Manage Quality *
Systems Development Life Cycle
Chapter 6: THE EIGHT STEP PROCESS FOCUS: This chapter provides a description of the application of customer-driven project management.
Project management Topic 4 Starting up a project.
Evaluate Phase Pertemuan Matakuliah: A0774/Information Technology Capital Budgeting Tahun: 2009.
Project Management.
Quick Recap.
Unit – I Presentation. Unit – 1 (Introduction to Software Project management) Definition:-  Software project management is the art and science of planning.
SEN 460 Software Quality Assurance. Bahria University Karachi Campus Waseem Akhtar Mufti B.E(C.S.E) UIT, M.S(S.E) AAU Denmark Assistant Professor Department.
6/6/ SOFTWARE LIFE CYCLE OVERVIEW Professor Ron Kenett Tel Aviv University School of Engineering.
SYSTEM ANALYSIS AND DESIGN LAB NARZU TARANNUM(NAT)
BUS OPERATOR WORKSTATION PROCUREMENT PROCESS ORGANIZATIONAL GUIDANCE TOOL 1 Version: February 19, 2016 TCRP Report 185.
Evaluation What is evaluation?
Advanced Software Engineering Dr. Cheng
Software Quality Assurance
Project Quality Management
Software Quality Control and Quality Assurance: Introduction
Project life span.
ECE361 Engineering Practice
Project Integration Management
TechStambha PMP Certification Training
Project Plan Template (Help text appears in cursive on slides and in the notes field)
Introduction to Systems Analysis and Design
Systems Analysis and Design
Effective Project Management: Traditional, Agile, Extreme
Sourcing Issues in outsourcing..
Presentation transcript:

MethodAssess System Assessment

Methoda Computers Ltd 2 List of Subjects 1. Introduction 2. Actions and deliverables 3. Lessons and decisions 5. In conclusion 4. Quality assurance

Methoda Computers Ltd 3 System Assessment - Definition  System assessment is a life-cycle phase in which the system is evaluated:  From the perspective of time  By a party from outside the project  The assessment stresses:  Malfunctions & problems that occurred  Benefits that can be cultivated  Anything else that happened, if unusual

Methoda Computers Ltd 4 System Assessment - Goal  Presenting the project comprehensively, in all its stages, so that lessons can be implemented at:  The project level  The organizational level  Infrastructure  Other projects Assess – Study – Learn – Act

Methoda Computers Ltd 5 When to assess a system  Methoda’s standard recommendations:  Size 3 and up, 6 months into production  Any project cancelled during or after Analysis  Schedule or cost deviation of 50% or more  Unexpected threat to project completion  Extremely negative risk analysis  At management’s discretion  Strategic considerations  A bad feeling about the project  Any other reason, any project size, any stage of the life cycle

Methoda Computers Ltd 6 List of Subjects 1. Introduction 2. Actions and deliverables 3. Lessons and decisions 5. In conclusion 4. Quality assurance

Methoda Computers Ltd 7 Lessons learned Holding the concluding discussion Producing the exec. presentation Distributing the Assessment doc Writing the Assessment Doc User Satisfaction Questionnaire Interviews Collecting input Informing the involved parties Preparing a work plan Appointing the assessor Starting the process Assessment Tasks Preliminary Activities Assessing the Project Final Activities

Methoda Computers Ltd 8 Assessment document Main Input Quality assurance documents Personal interviews Steering committee summaries, reviews & discussion summaries Contracts and agreements System documents (Analysis, Design, Testing)

Methoda Computers Ltd 9 Deliverables Preliminary Activities Assessing the Project Final Activities Work order Management & infrastructure commitment Assignments Work plan User Satisfaction Questionnaire Draft Assessment document Final Assessment document including executive summary Executive presentation Analysis of User Satisfaction Questionnaire

Methoda Computers Ltd 10 User Satisfaction Questionnaire 1. How satisfactory do you find overall system operation? 5 Excellent 4 Very good 3 Good 2 Fair 1 Poor 2. Judged by the Analysis requirements, how is the system? 5 Excellent 4 Very good 3 Good 2 Fair 1 Poor 3. How does the system contributes to your ongoing work? 5 Excellent 4 Very good 3 Good 2 Fair 1 Poor 4. How do you rate the system’s user-friendliness? 5 Excellent 4 Very good 3 Good 2 Fair 1 Poor

Methoda Computers Ltd 11 User Satisfaction Questionnaire 5. How do you rate the level of data security? 5 Excellent 4 Very good 3 Good 2 Fair 1 Poor 6. How do you rate the availability & reliability of the system? Poor 5 Excellent 4 Very good 3 Good 2 Fair 1 Poor 7. How do you rate change management and repair work? 5 Excellent 4 Very good 3 Good 2 Fair 1 Poor 8. How do you rate the Users’ forum? 5 Excellent 4 Very good 3 Good 2 Fair 1 Poor

Methoda Computers Ltd 12 Assessment Document  Executive summary  Background & general description  Findings & recommendations  Lessons for the organization  0. Administration  Participants in the Assessment  Relevant documentation  Assessment chronology, including noteworthy events

Methoda Computers Ltd 13 Assessment Document  What did Analysis establish?  What are the industry/organization standards?  What changed during system development?  What was actually implemented?  Are there problems? If so, what should be done?  Are there benefits? If so, can they be replicated elsewhere in the organization? Assessment according to the SCT: 1.Goals 2.Application 3.Technology 4.Implementation 5.Cost

Methoda Computers Ltd 14 Assessment Document  4.2 Project work plan – Assessment of project life cycle  Was each phase orderly?  How was the cost, in relation to norms of the industry or organization?  Was orderly documentation produced in accordance with MethodA?  Were custom procedures written?  Were systematic reviews conducted?

Methoda Computers Ltd 15 Assessment Document  Appendices  Analysis of the User Satisfaction Questionnaire  Additional topics  The process of analyzing alternatives and making decisions  Problem solving  Degree of user satisfaction  Use of methodologies

Methoda Computers Ltd 16 Taking the system off line System in development System in operation & maintenance Cancel or freeze the project Fix problems and prevent new problems Bring the system down temporarily for repair Bring a new system in or an old one back On-the-fly improvements Fix problems Improve next version Life cycle Decision Project-level Decisions

Methoda Computers Ltd 17 Lessons from Assessment  About project management for the organization  Time estimates and scheduling  Building and managing teams  Working with outsiders  Cost estimation  Professional training  Management tools & engineering tools

Methoda Computers Ltd 18 Lessons from Assessment  About the whole organization’s infrastructure  Applicability of new technology  Communications  With clients and users  With individual workers  With other departments  Time management  Knowledge sharing  Professional up-skilling

Methoda Computers Ltd 19 List of Subjects 1. Introduction 2. Actions and deliverables 3. Lessons and decisions 5. In conclusion 4. Quality assurance

Methoda Computers Ltd 20 Quality Assurance  Who is the Assessor, and how connected to the project?  Any similar assessments in the past?  What’s the exact mandate? Does it define what to assess and what not to?  Was a steering committee appointed?  Limited to the project, or with wider authority?  Was the mandate fulfilled, nothing skipped?  Are the lessons being applied?

Methoda Computers Ltd 21 List of Subjects 1. Introduction 2. Actions and deliverables 3. Lessons and decisions 5. In conclusion 4. Quality assurance

Methoda Computers Ltd 22 In conclusion  Words from the Sages  Who is wise? The one who learns from every person (Avot 4:1)  No one else brings wisdom like a person who brings experience (Milei Avot 10)  Words from the street  To err once is understandable, to err twice is unforgivable (Anon.)  Smart people get out of situations that wise people don’t get into (Anon.) Be a wise project manager, not a smart one

Methoda Computers Ltd 23