Content Comparison

Team Roles (5%)

Requirements & Constraint Analysis (20%)

• Team Roles: Role Allocation:  Have the team roles been allocated logically according to individual member strengths/goals?

• Has the entire team participated in the process of delegating team roles?

Requirements & Constraint Analysis (15%)

• Do the  

• Content: Do the requirements listed form a complete and accurate specification of the product?Have ?  Do the requirements outline a specification rather than an implementation? (PROBLEMS, not SOLUTIONS) . Is there a definition of what done looks like?

• Format: Have the requirements been listed in a consistent and readable format?Have  Have the requirements been organised in a logical hierarchy ?Have (logical grouping, sub-requirements, etc)? Have functional and non-functional requirements been differentiated?

• Is there a definition of what done looks like?

• Constraints: Are the constraints identified logical, valid and justified?Are  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 Persistence Layer: (1) Chosen (2) Justified appropriately(3) Considerations taken into account (4) Consideration of multiple options and elimination to decide upon the best one

• Application Layer: (1) Chosen(2) Justified appropriately(3) Considerations taken into account (4) Consideration of multiple options and elimination to decide upon the best one

• API Layer:(1) Chosen(2) Justified appropriately(3) Considerations taken into account(4) 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?one

• Deployment Layer:(1) Chosen(2) Justified appropriately(3) Considerations taken into account(4) Consideration of multiple options and elimination to decide upon the best one

Initial API Design (20%)

• Interface Breadth: Does the API design provide a near-complete solution to the specified requirements?Does  Does the API provide the ability to create, read, list, update and delete data in the service?

• Interface Quality: Have all required fields been included for each endpoint?

• Are the endpoint descriptions succinct and understandable?

• Is  Route names; Route description - succinct and understandable; CRUD method (GET, POST, PUT, DELETE); Parameters; Return values; Exceptional flows; Descriptions of composite parameter/return types; Is the interface well formatted and readable?

Project Planning (30%40%)

• Task Breakdown: Do tickets correspond to logical segmentations of work?Are  Are the tickets written at a technical level of abstraction? Have tickets been logically grouped under epics?  Have tasks been appropriately broken up into sub-tasks?Are  Does the plan provide a complete layout of the next sprint of work?

• Task Sequencing & Allocation: Have individuals been logically assigned to tasks? Are task allocations approximately equal across the team?Have  Have dependencies and prerequisites between tasks been highlighted?Have ? Is the backlog sequenced logically?

• Task Details: Are the ticket descriptions sufficient for someone picking up the work item with minimal understanding to begin work (links to supporting documentation, etc)? Have story points been logically allocated to tasks according to a specified structure?

• Have tasks been appropriately broken up into sub-tasks?

• Have  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%)

•  

• Meeting Minutes: Are meeting minutes well laid - out, detailed and insightful?Has Scrum Communications: Has the team undertaken Agile communications? (standups, sprint planning, sprint retrospective) Standups (at least 3 a week); Sprint Planning Meeting; Sprint Retrospective Meeting