methodassess n.
Download
Skip this Video
Loading SlideShow in 5 Seconds..
MethodAssess PowerPoint Presentation
Download Presentation
MethodAssess

Loading in 2 Seconds...

play fullscreen
1 / 23

MethodAssess - PowerPoint PPT Presentation


  • 115 Views
  • Uploaded on

MethodAssess. System Assessment. List of Subjects. 1. Introduction. 2. Actions and deliverables. 3. Lessons and decisions. 4. Quality assurance. 5. In conclusion. System Assessment - Definition. System assessment is a life-cycle phase in which the system is evaluated:

loader
I am the owner, or an agent authorized to act on behalf of the owner, of the copyrighted work described.
capcha
Download Presentation

PowerPoint Slideshow about 'MethodAssess' - duaa


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.While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server.


- - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - -
Presentation Transcript
methodassess

MethodAssess

System Assessment

list of subjects
List of Subjects

1. Introduction

2. Actions and deliverables

3. Lessons and decisions

4. Quality assurance

5. In conclusion

system assessment definition
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
system assessment goal
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

when to assess a system
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
list of subjects1
List of Subjects

1. Introduction

2. Actions and deliverables

3. Lessons and decisions

4. Quality assurance

5. In conclusion

assessment tasks

Starting the process

Collecting input

Distributing the Assessment doc

Appointing the assessor

Interviews

Producing the exec. presentation

Preparing a work plan

User Satisfaction Questionnaire

Holding the concluding discussion

Informing the involved parties

Writing the Assessment Doc

Lessons learned

Assessment Tasks

Final Activities

Preliminary Activities

Assessing the Project

main input

System documents

(Analysis, Design, Testing)

Contracts and agreements

Assessment document

Steering committee summaries,

reviews & discussion summaries

Quality assurance documents

Personal interviews

Main Input
deliverables

Final Activities

Preliminary Activities

Assessing the Project

Executive presentation

Work order

Management & infrastructure commitment

Analysis of User Satisfaction Questionnaire

Assignments

Final Assessment document including executive summary

Work plan

Deliverables

User Satisfaction Questionnaire

Draft Assessment document

user satisfaction questionnaire

5

5

5

5

4

4

4

4

3

3

3

3

2

2

2

2

1

1

1

1

Excellent

Excellent

Excellent

Excellent

Very good

Very good

Very good

Very good

Good

Good

Good

Good

Fair

Fair

Fair

Fair

Poor

Poor

Poor

Poor

User Satisfaction Questionnaire

1. How satisfactory do you find overall system operation?

2. Judged by the Analysis requirements, how is the system?

3. How does the system contributes to your ongoing work?

4. How do you rate the system’s user-friendliness?

user satisfaction questionnaire1

5. How do you rate the level of data security?

6. How do you rate the availability & reliability of the system?

Poor

7. How do you rate change management and repair work?

8. How do you rate the Users’ forum?

5

5

5

5

4

4

4

4

3

3

3

3

2

2

2

2

1

1

1

1

Excellent

Excellent

Excellent

Excellent

Very good

Very good

Very good

Very good

Good

Good

Good

Good

Fair

Fair

Fair

Fair

Poor

Poor

Poor

Poor

User Satisfaction Questionnaire
assessment document
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
assessment document1
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 Document

Assessment according

to the SCT:

  • Goals
  • Application
  • Technology
  • Implementation
  • Cost
assessment document2
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?
assessment document3
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
project level decisions
Project-level Decisions

On-the-fly improvements

Taking the system off line

Decision

Life cycle

System in development

Fix problems

Cancel or freeze the project

System in operation & maintenance

Fix problems and prevent new problems

Bring the system down temporarily for repair

Improve next version

Bring a new system in or an old one back

lessons from assessment
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
lessons from assessment1
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
list of subjects2
List of Subjects

1. Introduction

2. Actions and deliverables

3. Lessons and decisions

4. Quality assurance

5. In conclusion

quality assurance
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?
list of subjects3
List of Subjects

1. Introduction

2. Actions and deliverables

3. Lessons and decisions

4. Quality assurance

5. In conclusion

in conclusion
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