...
In this sprint, you will be expected to:
Within your team, allocate team roles.
Convert the initial specification for your assigned service category into a list of requirements.
Decide on a stack architecture for your service.
Identify any initial constraints that will affect the team’s performance in the project
Create an initial API interface design for your service.
Plan for the completion of work for the following sprint to complete a MVP of the service.
2. Team Roles
Based on your individual and collective strengths, discuss and as a team allocate the following roles:
...
Inside a Confluence page called Communications, document any reasoning and screenshots of communications outside MS Teams.
9. Marking Criteria
Criteria | Description |
|---|
Team Roles (5%) | |
Requirements & Constraint Analysis (15%) | Do the requirements listed form a complete and accurate specification of the product? Have the requirements been listed in a consistent and readable format? Have the requirements been organised in a logical hierarchy? Have functional and non-functional requirements been differentiated? Do the requirements outline a specification rather than an implementation? Is there a definition of what done looks like? Are the constraints identified logical, valid and justified? Are the suggested steps taken to exploit constraints feasible?
|
Initial Software Architecture Design (20%) | Have all relevant layers of the service been chosen? Is the stack logical and justified? Is there evidence of deliberation, consideration of multiple options and elimination to decide upon the best ones? Have factors and constraints been taken into account when deciding upon the stack?
|
Initial API Design (20%) | Does the API design provide a near-complete solution to the specified requirements? Does the API provide ability to create, read, list, update and delete data in the service? Have all required fields been included for each endpoint? Are the endpoint descriptions succinct and understandable? Is the interface well formatted and readable?
|
Project Planning (30%) | Do tickets correspond to logical segmentations of work? Are the tickets written at a technical level of abstraction? Have individuals been logically assigned to tasks? Are task allocations approximately equal? Have dependencies and prerequisites between tasks been highlighted? Have story points been logically allocated to tasks according to a specified structure? Have tasks been appropriately broken up into sub-tasks? Have priorities been logically allocated to tasks? Is the backlog sequenced logically? Have tickets been logically grouped under epics? Does the plan provide a complete layout of the next sprint of work?
|
Communications (10%) | Are meeting minutes well laid-out, detailed and insightful? Has the team been using a platform for regular communication? Has the team undertaken Agile communications? (standups, sprint planning, sprint retrospective)
|
10. Submission
For this sprint, we will take the state of your Jira board and Confluence space at the deadline as your submission. You do not need to run any submission commands.
...