CP Delivery 1: Analysis Grade
- Due No Due Date
- Points 100
This is a "placeholder" assignment for tracking the Analysis portion of Delivery 1: Solution Analysis.
You do not submit anything here.
Please submit your Delivery 1 here: Client Project Delivery 1 - Solution Analysis
Rubric
Please include a title
Keep in mind that 96 students have already been assessed using this rubric. Changing it will affect their evaluations.
Criteria | Ratings | Pts |
---|---|---|
Exec Summary - Project Request Recap
This maximum 1-page email to your client sponsor should serve as a very high-level summary of your Solution Analysis work. At a minimum it should include in a logical order a short description of (1) a quick recap of the original project request, (2) a recap of the root cause(s) that led to the proposed system (3) a short description of the proposed system’s key objectives and constraints, and (4) a summary of major project risks and reduction plans. Include all major items your client should know about your project using appropriate language for them (i.e. use terms they understand). CC your MIS 374 professor and include a link to the Solution Summary Mural.
threshold:
pts
|
pts
--
|
|
Exec Summary - Root Cause Recap Recap
threshold:
pts
|
pts
--
|
|
Exec Summary - Objectives & Constraints
threshold:
pts
|
pts
--
|
|
Exec Summary - Risk Summary
threshold:
pts
|
pts
--
|
|
Exec Summary - Email CC with link
threshold:
pts
|
pts
--
|
|
Stakeholders Analysis - Aligns with relevant subset of org?
Clearly identify all parties impacted by the project. Capture their level of impact on the project as well as their level of interest in or availability for the project.
threshold:
pts
|
pts
--
|
|
Stakeholders Analysis - All obvious included?
threshold:
pts
|
pts
--
|
|
Stakeholders Analysis - Interest/Availability
threshold:
pts
|
pts
--
|
|
Stakeholders Analysis - Influence
threshold:
pts
|
pts
--
|
|
Model As-Is Client Situation - Model provides clarity
Create a diagram(s) to model relevant aspects of the current “as-is” situation for your client. Explain why the type of diagram is best. Where do you need clarity the most? What insights from this model were relevant to your root cause analysis and/or potential solution(s)?
threshold:
pts
|
pts
--
|
|
Model As-Is Client Situation - Follows guidelines for selected model
threshold:
pts
|
pts
--
|
|
Model As-Is Client Situation - Relevance of type provided
threshold:
pts
|
pts
--
|
|
Model As-Is Client Situation - Where clarity is needed
threshold:
pts
|
pts
--
|
|
Model As-Is Client Situation - Shared insights gained
threshold:
pts
|
pts
--
|
|
Model As-Is Client Situation - Exercise feedback integrated?
threshold:
pts
|
pts
--
|
|
Root Cause Analysis - Problem Chain
This section should comprehensively address all issues and concerns for project success down to the basic symptoms driving need.
threshold:
pts
|
pts
--
|
|
Root Cause Analysis - Solution(s)
threshold:
pts
|
pts
--
|
|
Root Cause Analysis - Objectives
threshold:
pts
|
pts
--
|
|
Root Cause Analysis - Performance Criteria
threshold:
pts
|
pts
--
|
|
Root Cause Analysis - Constraints
threshold:
pts
|
pts
--
|
|
Root Cause Analysis - Exercise feedback integrated?
threshold:
pts
|
pts
--
|
|
To-Be Concept Diagram - Clarity
Concept diagram should illustrate the proposed system. This diagram should tie closely to the objectives of the proposed solution(s) in the root cause analysis and should tie closely to the identified user stories.
threshold:
pts
|
pts
--
|
|
To-Be Concept Diagram - Ties to Root Cause Objectives?
threshold:
pts
|
pts
--
|
|
To-Be Concept Diagram - Ties to Stakeholders?
threshold:
pts
|
pts
--
|
|
To-Be Concept Diagram - Follows 5 sketching rules
threshold:
pts
|
pts
--
|
|
To-Be Concept Diagram - Exercise feedback intgrated?
threshold:
pts
|
pts
--
|
|
User Stories - Correct format
Identify all user stories and tie directly to the to-be concept diagram. User Stories should follow correct format.
threshold:
pts
|
pts
--
|
|
User Stories - Tie to to-be concept
threshold:
pts
|
pts
--
|
|
User Stories - No missing
threshold:
pts
|
pts
--
|
|
User Stories - Sized right
threshold:
pts
|
pts
--
|
|
User Stories - Exercise feedback intergrated?
threshold:
pts
|
pts
--
|
|
User Acceptance Criteria - Relates to story
acceptable
threshold:
pts
|
pts
--
|
|
User Acceptance Criteria - Clear/actionalable?
threshold:
pts
|
pts
--
|
|
User Acceptance Criteria - Feedback integrated?
threshold:
pts
|
pts
--
|
|
Feasibility Matrix - All stories included?
Co-create a feasibility matrix with your client that includes all proposed user stories.
threshold:
pts
|
pts
--
|
|
Feasibility Matrix - Difficulty
threshold:
pts
|
pts
--
|
|
Feasibility Matrix - Value
threshold:
pts
|
pts
--
|
|
Feasibility Matrix - Exercise feedback integrated?
threshold:
pts
|
pts
--
|
|
Non-Functional Context - Maintainability context
Address Maintainability, Portability, Scalability, Security, Performance, and Accessibility context and requirements for the project.
threshold:
pts
|
pts
--
|
|
Non-Functional Requirements - Maintainability
threshold:
pts
|
pts
--
|
|
Non-Functional Context - Portability
threshold:
pts
|
pts
--
|
|
Non-Functional Requirements - Portability
threshold:
pts
|
pts
--
|
|
Non-Functional Context - Scalability
threshold:
pts
|
pts
--
|
|
Non-Functional Requirements - Scalability
threshold:
pts
|
pts
--
|
|
Non-Functional Context - Security
threshold:
pts
|
pts
--
|
|
Non-Functional Requirements - Security
threshold:
pts
|
pts
--
|
|
Non-Functional Context - Performance
threshold:
pts
|
pts
--
|
|
Non-Functional Requirements - Performance
threshold:
pts
|
pts
--
|
|
Non-Functional Context - Accessibility
threshold:
pts
|
pts
--
|
|
Non-Functional Requirements - Accessibility
threshold:
pts
|
pts
--
|
|
Evaluation Table - List of possible options
Used to help determine system solution. Make research of alternatives clear. Be sure to clearly indicate what alternative the client chose.
threshold:
pts
|
pts
--
|
|
Evaluation Table - User Story Coverage
threshold:
pts
|
pts
--
|
|
Evaluation Table - Advantages
threshold:
pts
|
pts
--
|
|
Evaluation Table - Disadvantages
threshold:
pts
|
pts
--
|
|
Evaluation Table - Cost breakdown
threshold:
pts
|
pts
--
|
|
Evaluation Table - Cost (UOM)
threshold:
pts
|
pts
--
|
|
Evaluation Table - Questions/Unknowns
threshold:
pts
|
pts
--
|
|
Evaluation Table - Client Decision
threshold:
pts
|
pts
--
|
|
Client Background/Overview - Clear & Concise
Address the following items: a) identify the organization structure broadly, b) pinpoint the part(s) of the organization that the proposed system affects, and c) address impact of the system and benefits to areas of strategy, management, and operations of the organization that is particularly relevant in the context of the system
threshold:
pts
|
pts
--
|
|
Client Background/Overview - Parts of org affected
threshold:
pts
|
pts
--
|
|
Client Background/Overview - Strategic Impact
threshold:
pts
|
pts
--
|
|
Client Background/Overview - Managerial Impact
threshold:
pts
|
pts
--
|
|
Client Background/Overview - Operational Impact
threshold:
pts
|
pts
--
|
|
Organization Chart [Optional]
This should be labeled “ABC Corporation Organization Chart.” Its purpose is to show the organizational roles of the clients you are working with.
threshold:
pts
|
pts
--
|
|
Empathy Map [Optional]
Create an empathy map for your main client/stakeholder in your project.
threshold:
pts
|
pts
--
|
|
As-Is Systems Architecture Checklist [Optional]
Identify the necessary software tools and hardware environment for the as-is system using the provided checklist.
threshold:
pts
|
pts
--
|
|
Additional To-Be Models or Diagrams [Optional]
Any additional models or diagrams – not “types” of models/diagrams, just models/diagrams. The models/diagrams you include should help your team better understand the clients’ problems and/or help your client more clearly understand various aspects of your proposed solution.
threshold:
pts
|
pts
--
|
|
Risk Evaluation & Risk Reduction [Optional]
Complete a full risk analysis with clear rationales for each risk score and clear next steps or mitigations for 0s and -1s
threshold:
pts
|
pts
--
|
|
To-Be Architecture Checklist [Optional]
Identify the necessary software tools and hardware environment for the as-is system using the provided checklist.
threshold:
pts
|
pts
--
|
|
Sample Input/output Documents/Sample Data from Client [Optional]
Include documents provided by your client and any documents you have created or obtained from the client.
threshold:
pts
|
pts
--
|