Agile Methodology

profilej71091
AgileMethodologyScoringGuide.pdf

4/17/2021 Agile Methodology Scoring Guide

https://courserooma.capella.edu/bbcswebdav/institution/IT/IT3345/190100/Scoring_Guides/u01a1_scoring_guide.html 1/1

Agile Methodology Scoring Guide

Due Date: End of Unit 1 Percentage of Course Grade: 17%.

CRITERIA NON-PERFORMANCE BASIC PROFICIENT DISTINGUISHED

Justify why an Agile methodology is appropriate for CapraTek.

23%

Does not justify why an Agile methodology is appropriate for CapraTek.

Justifies a choice of Agile methodology that is ill-suited for CapraTek or provides a justification that is unclear, disorganized, or unconvincing.

Justifies why an Agile methodology is appropriate for CapraTek.

Justifies why an Agile methodology is appropriate for CapraTek by using specific examples to support it.

Create an activity diagram that properly illustrates an Agile life cycle methodology.

23%

Does not create an activity diagram.

Creates an activity diagram that poorly illustrates an Agile life cycle methodology.

Creates an activity diagram that properly illustrates an Agile life cycle methodology.

Creates an activity diagram that effectively illustrates an Agile life cycle methodology using UML conventions and symbols.

Explain each activity or phase depicted on a UML diagram and how they relate to the software development process.

22%

Does not explain each activity or phase depicted on a UML diagram and how they relate to the software development process.

Explains each activity or phase depicted on a UML diagram incompletely or does not explain how they relate to the software development process.

Explains each activity or phase depicted on a UML diagram and how they relate to the software development process.

Explains each activity or phase depicted on a UML diagram and how they relate to the software development process in great detail that demonstrates superior understanding of Agile development methodologies.

Describe how Agile activities or phases might manifest themselves in a business scenario.

22%

Does not describe how Agile activities or phases might manifest themselves in a business scenario.

Describes how Agile activities or phases might manifest themselves in a business scenario in an inaccurate or confusing manner.

Describes how Agile activities or phases might manifest themselves in a business scenario.

Describes how Agile activities or phases might manifest themselves in a business scenario in great detail that includes specific references to the business scenario.

Integrate visual elements with writing that generally clarify or highlight key points. 10%

Integrates visual elements with writing that do not clarify or highlight key points.

Integrates visual elements with writing that somewhat clarify or highlight key points.

Integrates visual elements with writing that generally clarify or highlight key points.

Integrates visual elements with writing that clearly and directly clarify or highlight key points.