Agile Delivery Framework

Points: 100

Assignment 2: Agile Delivery Framework

Criteria

Unacceptable

Below 60% F

Meets Minimum Expectations

60-69% D

Fair

70-79% C

Proficient

80-89% B

Exemplary

90-100% A

1. Develop a project schedule that includes at least two (2) phases and twelve (12) tasks under the Agile delivery framework through the use of MS Project or Excel.

Weight: 15%

Did not submit or incompletely developed a project schedule that includes at least two (2) phases and twelve (12) tasks under the Agile delivery framework through the use of MS Project or Excel.

Insufficiently developed a project schedule that includes at least two (2) phases and twelve (12) tasks under the Agile delivery framework through the use of MS Project or Excel.

Partially developed a project schedule that includes at least two (2) phases and twelve (12) tasks under the Agile delivery framework through the use of MS Project or Excel.

Satisfactorily developed a project schedule that includes at least two (2) phases and twelve (12) tasks under the Agile delivery framework through the use of MS Project or Excel.

Thoroughly developed a project schedule that includes at least two (2) phases and twelve (12) tasks under the Agile delivery framework through the use of MS Project or Excel.

2. Determine the product vision and provide strategies for how to conduct the envisioning practice.  Weight: 15%

Did not submit or incompletely determined the product vision and did not submit or incompletely provided strategies for how to conduct the envisioning practice. 

Insufficiently determined the product vision and insufficiently provided strategies for how to conduct the envisioning practice. 

Partially determined the product vision and partially provided strategies for how to conduct the envisioning practice. 

Satisfactorily determined the product vision and satisfactorily provided strategies for how to conduct the envisioning practice. 

Thoroughly determined the product vision and thoroughly provided strategies for how to conduct the envisioning practice. 

3. Determine the main roles of the Agile project team and explain whether the product manager should be from the IT field or non-IT related field.

Weight: 20%

Did not submit or incompletely determined the main roles of the Agile project team and did not submit or incompletely explained whether the product manager should be from the IT field or non-IT related field.

Insufficiently determined the main roles of the Agile project team and insufficiently explained whether the product manager should be from the IT field or non-IT related field.

Partially determined the main roles of the Agile project team and partially explained whether the product manager should be from the IT field or non-IT related field.

Satisfactorily determined the main roles of the Agile project team and satisfactorily explained whether the product manager should be from the IT field or non-IT related field.

Thoroughly determined the main roles of the Agile project team and thoroughly explained whether the product manager should be from the IT field or non-IT related field.

4. Explain how iteration works in this project. Support your rationale.

Weight: 15%

Did not submit or incompletely explained how iteration works in this project. Did not submit or incompletely supported your rationale.

Insufficiently explained how iteration works in this project. Insufficiently supported your rationale.

Partially explained how iteration works in this project. Partially supported your rationale.

Satisfactorily explained how iteration works in this project. Satisfactorily supported your rationale.

Thoroughly explained how iteration works in this project. Thoroughly supported your rationale.

5. Take a position on whether stories are important in the Agile delivery framework and explain why or why not. Include at least two feature-story examples to support your explanation.

Weight: 20%

Did not submit or incompletely took a position on whether stories are important in the Agile delivery framework and did not submit or incompletely explained why or why not. Did not submit or incompletely included at least two feature-story examples to support your explanation.

Insufficiently took a position on whether stories are important in the Agile delivery framework and insufficiently explained why or why not. Insufficiently included at least two feature-story examples to support your explanation.

Partially took a position on whether stories are important in the Agile delivery framework and partially explained why or why not. Partially included at least two feature-story examples to support your explanation.

Satisfactorily took a position on whether stories are important in the Agile delivery framework and satisfactorily explained why or why not. Satisfactorily included at least two feature-story examples to support your explanation.

Thoroughly took a position on whether stories are important in the Agile delivery framework and thoroughly explained why or why not. Thoroughly included at least two feature-story examples to support your explanation.

6. 3 references

Weight: 5%

No references provided

Does not meet the required number of references; all references poor quality choices.

Does not meet the required number of references; some references poor quality choices.

Meets number of required references; all references high quality choices.

Exceeds number of required references; all references high quality choices.

7. Clarity, writing mechanics, and formatting requirements

Weight: 10%

More than 8 errors present

7-8 errors present

5-6 errors present

3-4 errors present

0-2 errors present