CIS 443
|
Points: 100 |
Assignment 3: Release Planning |
||||
|
Criteria |
Unacceptable Below 60% F |
Meets Minimum Expectations 60-69% D |
Fair 70-79% C |
Proficient 80-89% B |
Exemplary 90-100% A |
|
1. Draw a diagram to highlight the product road map and product life cycle through the use of graphical tools in Visio, or an open source alternative such as Dia. Weight: 15% |
Did not submit or incompletely drew a diagram to highlight the product road map and product life cycle through the use of graphical tools in Visio, or an open source alternative such as Dia. |
Insufficiently drew a diagram to highlight the product road map and product life cycle through the use of graphical tools in Visio, or an open source alternative such as Dia. |
Partially drew a diagram to highlight the product road map and product life cycle through the use of graphical tools in Visio, or an open source alternative such as Dia. |
Satisfactorily drew a diagram to highlight the product road map and product life cycle through the use of graphical tools in Visio, or an open source alternative such as Dia. |
Thoroughly drew a diagram to highlight the product road map and product life cycle through the use of graphical tools in Visio, or an open source alternative such as Dia. |
|
2. Provide at least two (2) iterations and twelve (12) tasks related to development on mobile devices through the use of MS Project. Weight: 10% |
Did not submit or incompletely provided at least two (2) iterations and twelve (12) tasks related to development on mobile devices through the use of MS Project. |
Insufficiently provided at least two (2) iterations and twelve (12) tasks related to development on mobile devices through the use of MS Project. |
Partially provided at least two (2) iterations and twelve (12) tasks related to development on mobile devices through the use of MS Project. |
Satisfactorily provided at least two (2) iterations and twelve (12) tasks related to development on mobile devices through the use of MS Project. |
Thoroughly provided at least two (2) iterations and twelve (12) tasks related to development on mobile devices through the use of MS Project. |
|
3. Suggest strategies on calculating relative value points and monetary value points. Weight: 15% |
Did not submit or incompletely suggested strategies on calculating relative value points and monetary value points. |
Insufficiently suggested strategies on calculating relative value points and monetary value points. |
Partially suggested strategies on calculating relative value points and monetary value points. |
Satisfactorily suggested strategies on calculating relative value points and monetary value points. |
Thoroughly suggested strategies on calculating relative value points and monetary value points. |
|
4. Speculate on the associated risks regarding the development on mobile devices and provide strategies to mitigate those risks. Weight: 15% |
Did not submit or incompletely speculated on the associated risks regarding the development on mobile devices and did not submit or incompletely provided strategies to mitigate those risks. |
Insufficiently speculated on the associated risks regarding the development on mobile devices and insufficiently provided strategies to mitigate those risks. |
Partially speculated on the associated risks regarding the development on mobile devices and partially provided strategies to mitigate those risks. |
Satisfactorily speculated on the associated risks regarding the development on mobile devices and satisfactorily provided strategies to mitigate those risks. |
Thoroughly speculated on the associated risks regarding the development on mobile devices and thoroughly provided strategies to mitigate those risks. |
|
5. Provide at least one (1) example of maintenance stories based on the context of the project. Weight: 15% |
Did not submit or incompletely provided at least one (1) example of maintenance stories based on the context of the project. |
Insufficiently provided at least one (1) example of maintenance stories based on the context of the project. |
Partially provided at least one (1) example of maintenance stories based on the context of the project. |
Satisfactorily provided at least one (1) example of maintenance stories based on the context of the project. |
Thoroughly provided at least one (1) example of maintenance stories based on the context of the project. |
|
6. Provide at least one (1) example of performance cards based on the context of the project. Weight: 15% |
Did not submit or incompletely provided at least one (1) example of performance cards based on the context of the project. |
Insufficiently provided at least one (1) example of performance cards based on the context of the project. |
Partially provided at least one (1) example of performance cards based on the context of the project. |
Satisfactorily provided at least one (1) example of performance cards based on the context of the project. |
Thoroughly provided at least one (1) example of performance cards based on the context of the project. |
|
7. 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. |
|
8. 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 |