Manual projects

Development

On this page most information about the Capturum Software Group is found in a central place. This so you can read and find the information here whenever you need it.

This document is being filled continuously . So if you are missing any information please don’t hesitate to ask.

Jira – flow

We are using 2 boards on Jira to manage our projects:

  • Client/PM
  • Developer

When creating a new project on Jira please use the explanation found here. Below you find a explanation per lane:

Client/PM Board:

  1. Backlog-Concept: this lane contains all future functionalities which can be created and changed by the client, lead, testers and PM. Developers can use comments to ask questions and note made decisions.
  2. Selected for Development: a selection made by (or after consultation with) the client. The functionalities in this lane are the ones selected for next refinement session. – Client/PM change
  3. Refined: tickets from selected for development will be refined by Client, Lead (optionally UX) and Projectmanagement. When done so the tickets moves to ‘refined’. – PM change
  4. Pokered: all refined ticket are pokered by the whole team. Questions are to be asked prior to this meeting. When an estimation is added to the ticket the ticket is moved from ‘refined’ to ‘pokered’. From here sprints can be planned. – PM change
  5. Sprint to do: depending on the team formation a number of points can be fit in a sprint. Pokered tickets are added to the status ‘sprint to do’ and placed in a sprint. – PM change
  6. In development: developers are working on the ticket, it is somewhere along the development process. To know more details a client should take a look at the Developer board. – Developer changes
  7.  Ready for Acceptance: the ticket is developed and tested internally and is ready to be deployed on the acceptance server where it is released to the client. – Tester/PM change
  8. In Acceptance: tickets in this lane are available for client testing. – Lead change (after build)
  9. Ready for release: clients put tickets in this lane once they have tested the functionality on acceptance and approved them for release. – Client change
  10. Done: after release on production is done tickets are finished and moved to this lane. – Lead change (after build)

Developer Board:

This board contains all statuses that are combined in the “In development” lane on Client/PM board:

  1. Sprint to do: tickets in this lane are selected for the active sprint to be developed.
  2. In Progress: when starting a ticket a developer makes sure to assign the ticket to themself and change the status to “in progress”. – Developer change
  3. In Review: when local development and testing is done a pull request (PR, see ‘Technical Reviewing’) is made and the ticket is put in this lane. – Developer change
  4. Ready for test: after possible changed are done and approves are received the ticket can be deployed to test on the next release. – Developer change
  5. In Test: functionality is available on test server. The developer creating the functionality tests his functionality one more time and fixes possible bugs. – Developer (after build)
  6. Ready for Acceptance: from the ‘In Test’ lane testing and PM can check delivered functionality. If any error/fault/bug is found the ticket is put back to ‘redo’ which is shown in the “Sprint to do” lane. When a story is met and all is good the ticket proceeds to ‘ready for acceptance’ and a comment is placed.  – Tester/PM change