Assessment Case Study
IFB295 IT Project Management
Semester 1 – 2022
Name …………………….. Assessment 1 – Agile Techniques
Due ………………………. Week 5 Friday 8/4/2022 11:59pm
Weight …………………… 20%
Type ……………………… Group
Submit …………………… Zip your files and submit one zipped file via Blackboard
Please refer to the Study Guide document on Blackboard the Unit Details page for information about feedback, late submissions, extensions, and reviews.
Your team will carry out Scrum activities to plan and estimate project requirements for developing an IT solution for the given case study. So, your team will analyse the case study and produce the following Scrum artefacts of User Stories as a Product Backlog, Releases Plan, and First Sprint Plan.
Instructions
This assessment is a group assessment. You MUST work in groups.
Any member in the team can submit this assessment, as long as the team member is registered in the blackboard group allocated to the team.
Only one submission is required per team.
Assignment submissions MUST be a single PDF file properly identified (listing all student names and number). Please maintain these files on your team’s Trello board.
You will complete the Assessment Tasks listed below.
Academic Honesty
Any action or practice on your part which would defeat the purposes of assessment is regarded as academic dishonesty. The penalties for academic dishonesty are provided in the Student Rules. For more information, consult the QUT Library resources for avoiding plagiarism.
Resources
The following resources may assist with the completion of this task:
- Refer to the Case Study document.
- Refer to the criteria sheet included in this document.
- Refer to tutorial materials and any lecture videos.
- Refer to the recommended reading list.
Questions
Questions related to the assessment should be directed to the teaching team during the workshops or drop-in sessions and via Trello.
The teaching team will not be available to answer questions outside business hours, nor in the hours immediately before the assessment is due.
Assessment Tasks
Your team will carry out Scrum activities to plan and estimate project requirements for developing an IT solution for the ExerciseRus – Case Study.
So, your team will analyse the case study and produce the following.
You will be planning using a sprint duration of two weeks.
Scrum artefacts for submission:
- User Stories (also called Product Backlog) – The Product Backlog should contain user stories that meet the criteria described in the Assessment 1 Criteria Sheet.docx (see below.) Use the file named Story Card Template.pptx (available on Blackboard Assessment 1 page) or an Excel spread sheet as explained in the lecture/tutorial to create this document.
- Releases Plan – Assemble user stories into logical groups for releases and subsequent decomposition of the first release into a sprint. Refer to the example “Release and Sprint Plan – Example.pdf” document (available on Blackboard Assessment 1 page). Use the template file named “Release and Sprint Plan.docx” (available on Blackboard Assessment 1 page) to create your Releases Plan.
- First Sprint Plan – Identify stories in Release 1 and use those for completing the First Sprint by decomposing them into implementation tasks. Refer to the example “Release and Sprint Plan – Example” document. Use the template file named “Release and Sprint Plan.docx” to create your team’s First Sprint Plan.
Three artefacts to submit are a completed;
GroupName Story Card Template.pptx
GroupName Sprint Plan.docx
GroupName Release and Sprint Plan.docx
Zip these documents and submit the zipped file before the submission deadline date using the link available on Blackboard Assessment 1 page. Also, please maintain these files on your team’s Trello board.
Criteria Sheet (follows)
| IFB295 Assessment 1 Marking Criteria | |||||
| Marks | |||||
| Story Cards | Your submitted story cards demonstrate that | ||||
| 14 – 12 | 11 – 10 | 9 – 8 | 7 – 6 | < 6 | |
| Marks (14 marks) | the large majority of your stories demonstrate very good application of all the principles of INVEST and each story is a clear expression of a single idea behind the requirement.your stories represent a wide range of features that have a balance of moderate to challenging requirements that deliver high business value.all stories have been prioritised with the client using MoSCoW as clearly indicated on card.all stories have been realistically and consistently estimated with story points.the large majority of stories have acceptance criteria that provide a clear understanding of the client’s goal & a clear boundary of scope.almost all acceptance criteria can clearly be implemented as tests. | the large majority of your stories demonstrate good application of all the principles of INVEST and each story is a clear expression of a single idea behind the requirement.your stories represent a range of features that have a balance of moderate to challenging requirements that deliver high business value.almost all stories have been prioritised with the client using MoSCoW. most stories have been consistently and fairly realistically estimated with story points.the majority of stories have acceptance criteria that provide a clear understanding of the client’s goal & a general understanding of scope.most acceptance criteria can clearly be implemented as tests. | the majority of your stories demonstrate good application of most the principles of INVEST and each story expresses a single idea behind the requirement.your stories represent a range of features that have a balance of easy to challenging requirements that deliver focussed business value.all stories in the first release have been prioritised with the client using MoSCoW.all stories have been consistently estimated with story points.the majority of stories have acceptance criteria that provide a fairly clear understanding of the client’s goal and some understanding of scope.most acceptance criteria seem to be implementable as tests. | the majority of your stories demonstrate application of the principles of INVEST and a large majority of your stories express a single idea behind the requirement.your stories represent a range of features that have a balance of easy to moderately challenging requirements that deliver business value.most stories have been prioritised using MoSCoW, with clear direction from the client.most stories have been fairly consistently estimated with story points.the majority of stories have acceptance criteria that provide a general understanding of the client’s goal and possibly little understanding of scope.a majority of acceptance criteria seem to be implementable as tests | some of your stories demonstrate application of the principles of INVEST or only some stories express a single idea behind the requirement.your stories represent a narrow range of features or are a set of requirements with little challenge or that deliver little coherent business value.some stories have been prioritised with the client using MoSCoW. some stories have been estimated or estimates are not consistent across stories.some story acceptance criteria provides at best a general understanding of the client’s goal and /or no real understanding of scope.some acceptance criteria seem difficult to implement as tests. |
| 4 | 3 | 2 | 1 | < 1 | |
| Process | Your team has demonstrated its application of agile principles in your project by | ||||
| Marks (4 marks) | being well prepared for workshops.showing a great deal of initiative in preparing for the project.developing a positive team culture.the developers having a clear shared understanding of the project’s goals and your stories. | being prepared for workshops.showing good initiative in preparing for the project.starting to develop a positive team culture.the developers having a shared understanding of the project’s goals and most of your stories. | being mostly prepared for workshops.showing initiative in preparing for the project.starting to develop a positive team culture.the developers having a shared understanding of the project’s goals. | being partially prepared for workshops.showing a little initiative in your preparation for the project.possibly starting to develop a positive team culture.the developers having a general shared understanding of the project’s goals. | rarely being prepared for workshops.showing little to no initiative in your preparation for the project.not starting to develop a positive team culture.the developers not having a shared understanding of the project’s goals. |
| 5 | 4 | 3 | 2 | 1 | |
| Release Plan | Your release plan demonstrates that | ||||
| Weight (5 marks) | you have a well-established backlog that provides a clear indication of the client’s goals and direction for the product.each release delivers important business value to the client through a cohesive feature set.client priorities are clearly reflected in the delivery dates. the client can see a clear, easy to understand, and believable schedule of when features will be released. | you have a good backlog that provides a fairly clear indication of the client’s goals and direction for the product.each release delivers important business value to the client but could be more cohesive.client priorities are reflected in the delivery dates.the client can see a clear and believable schedule of when features will be released. | you have a fairly good backlog that provides a fairly clear indication of the client’s goals.each release delivers business value to the client but releases have no clear theme.most client priorities are clearly reflected in the delivery dates.the client can see a clear and reasonably feasible schedule of when features will be released. | you have a reasonable backlog that provides some indication of the client’s goals.each release delivers business value to the client.most client priorities are reflected in the delivery dates.the client can fairly easily see an arguably feasible schedule of when features will be released. | you have enough in the backlog for more than one sprint but there is little indication of the client’s goals.some releases may deliver business value to the client.client priorities cannot easily be seen in the delivery schedule.schedule does not seem to be feasible. |
| 7 – 6 | 5 – 4 | 3 – 2 | 1 | < 1 | |
| Sprint Plan | Your sprint plan demonstrates that you have | ||||
| Weight (7 marks) | selected a coherent group of stories that will achieve the sprint goal and deliver the highest possible value to the client.selected stories for the sprint that have almost no dependencies and which setup following sprints to complete the release.broken the stories into small, independent tasks that cover all aspects of the stories.realistically and consistently estimated the effort required for each task.realistically considered the amount of work that can feasibly be done in the sprint considering the people and skills in your team, time available, and task estimates. | selected a coherent group of stories that will achieve the sprint goal and deliver high value to the client.selected stories for the sprint that have few dependencies and which setup following sprints to complete the release.broken the stories into small, independent tasks.fairly realistically and consistently estimated the effort required for each task.realistically considered the amount of work that can feasibly be done in the sprint giving some consideration to the people and skills in your team, time available, and task estimates. | selected a coherent group of stories that will mostly achieve the sprint goal and deliver high value to the client.selected stories for the sprint that have few dependencies and are predecessors for stories in later sprints.broken the stories into reasonable and mostly independent tasks.consistently estimated the effort required for most tasks.fairly realistically considered the amount of work that can feasibly be done in the sprint giving some consideration to the people and skills in your team, time available, and task estimates. | selected a group of stories that will deliver high value to the client, but which may not be a coherent feature set.selected stories for the sprint that are a logical starting point for the first release.broken the stories into reasonable tasks.fairly consistently estimated the effort required for most tasks.considered the amount of work that can feasibly be done in the sprint but with little consideration to the people and skills in your team, time available, and task estimates. | selected a group of stories that do not map to a clear sprint goal or which deliver lower value features to the client.put little planning into the selection of stories for the first sprint.broken the stories into tasks that are too dependent on each other or are too large.not provided tasks for all stories.unrealistically or inconsistently estimated the effort required for many tasks; or did not provide meaningful estimates.not realistically considered the amount of work that can feasibly be done in the sprint or that is required by the stories that have been selected. |
Get expert help for IFB295 IT Project Management – Assessment Case Study and many more. 24X7 help, plag free solution. Order online now!
