UNDER CONSTRUCTION AND LIKELY TO CHANGE

The objective is to assess project progress and team maturation that occurred during the past time period. Grade weighting depends on where you are in the lifecycle and the team's experiences and capabilities. The three key activities are:

1 Requirements Management

  • Created in confluence
  • Reviewed by team or client
  • Updated by team or client
  • Tasks/Stories created or updated and are these changes in an updated backlog

2 Development Activities

Design Points

  • Did you create UML, static or dynamic diagrams, and their quality
  • Discussion of technologies selected: Is there a thread on confluence discussing this?

Test Specifications

  • Did you create and review test specifications for components?
  • Did you do usability assessments for UI? What were the results and were any changes necessary?

Dev environments setup

  • Core environment: machines, storage, network (firewall, internet access)
  • Tools installed: e.g. tomcat, mysql, mongo, …
  • Confluence: set up
  • Continuous integration: selected and set up (e.g. Jenkins), links to git, jira/confluence, slack and others as needed.
  • Slack (or Hipchat): Client and teaching team have access. Linked to jira

Backlog Management

  • Status of backlog: story points/tasks being added, completed, or moved out of sprint or scope
  • Dev status: (by dev) number of jira tickets assigned, worked and closed
  • Test reviews: (by dev) number of test specs or usability specs reviewed. Which were passed and which were referred for more work.
  • Bugs: (by dev) identified, worked and currently in progress, slain
  • Retrospective on sprint plan: did the team accomplish what it set out to do? Did it accomplish more than expected or less? Why?

3 Results

  • What did you achieve this sprint?
  • Live working code: new features, reworked features
  • Feedback from use: who used it and what was the feedback
  • Release doc