Plan
Overview of the general development process and planning in the project.
This document is heavily drafting!
1 Appkit Planning
1.1 Repo Overview
| URL | Short Description | Status |
|---|---|---|
| appkit-admin-test | Selenium Tests for the Backend | active |
| appkit-feedback | Space to collect user feedback | active |
| appkit-manual | The user manual | active |
| appkit-mobile | The App | active |
| appkit-ops | GitOps to instantiate the backend | active |
| appkit-steering | Meta repo to document the work of the appkit team | starting |
| appkit | The Backend | active |
1.2 Overall Development Process
The overall development process is roughly organized into three phases.
- Planning
- Development
- Release
Each phase is defined by a series of steps to produce some main artefacts that are required to lead over into the next phase.
Main artefacts are
- User Stories
- Tested Code
- Deployments
The process can be characterised as iterative and incremental. In the diagram this is expressed by various ‘cycles’ where certain steps are repeatedly performed in a defined order.
The process is driven by multiple series of regular working meetings.
| Interval | Name | Goal | Participants | Initiator |
|---|---|---|---|---|
| Daily | Developer Daily | Interchange between devs. Blockers, ongoing tasks, etc. | Developers, Product Owner | Product Owner |
| Weekly | Product Session | Identify and Explore new requirements, Discuss Bugs and User Feedback | Service Manager, Domain Experts | Service Manager |
| Weekly | Refinement Session | Pick up requirements and create User Stories | Service Manager, Product Owner, Domain Experts - as required | Service Manager |
| Weekly | TechSpec and Estimation | Refine User Stories with technical specifications. Estimate the workload/costs. | Developers, Product Owner | Product Owner |
| Bi-Weekly | Planning | Pick up User Stories for next development cycle | Service Manager, Product Owner | Service Manager |
| Quarterly | Release Planning | Plan releases | Service Manager, Product Owner, Team as required | Service Manager |
| Quarterly | Retrospective | Discuss the process: Start, Stop, Continue | Service Manager, Product Owner, Team as required | Service Manager |
Each meeting is accompanied by a board.
| Name | Location | Note | Status |
|---|---|---|---|
| Product Board | Internal Board. Asana | The board is mainly used to organize our weekly Product Session. | active |
| User Feedback Board | appkit-feedback | It is more a list of issues to collect user feedback. | active |
| Developer Board - Backlog | gesis-appkit | The main board. | in migration |
| Release Planning - Board | appkit-ops | Organizes Rollouts and QA. | in migration |
1.3 Gitlab Boards Conventions
Columns
| Name | Function | Boards | Status |
|---|---|---|---|
| Open | gitlab default | ||
| Discussion | in migration | ||
| Ready To Implement | in migration | ||
| In Progress | in migration | ||
| In Code Review | in migration | ||
| QA | in migration | ||
| Closed | gitlab default |
Labels
| Name | Function | Level | Status |
|---|---|---|---|
| Backlog | group | in migration | |
| Bug/Error | group | in migration | |
| Critical Issue | group | in migration | |
| Design/UX/UI | group | in migration | |
| DevOps | group | in migration | |
| Discussion | group | in migration | |
| Error | group | in migration | |
| Export | group | in migration | |
| In Progrss | group | in migration | |
| Internal Discussion | group | in migration | |
| Legal Requirements | group | in migration | |
| MVP | group | in migration | |
| Mananging Projects | group | in migration | |
| QA | group | in migration | |
| Ready To implement | group | in migration | |
| Support | group | in migration | |
| Survey Feature | group | in migration | |
| User Management | group | in migration | |
| In code review | group | in migration | |
| side-menu | group | in migration | |
| testing(closed) | group | in migration | |
| testing(open) | group | in migration | |
| under observation | group | in migration | |
| QA-Staging-Passed | used in rollout board | group | migrated |
| QA-Production-Passed | used in rollout board | group | migrated |
| on prod | used in rollout board | group | migrated |
| on staging | used in rollout board | group | migrated |
| e2e-Production-Passed | used in rollout board | group | migrated |
| e2e-Staging-Passed | used in rollout board | group | migrated |
1.4 Templates and Definitions
User Story Template
| Field | Function | Session |
|---|---|---|
| Name | A short name | |
| Description | The actual story: “As a <persona>, I <want to>, <so that>.” | Product Session, Refinement |
| Requirements | Description from domain expert in clear language | Product Session, Refinemen |
| Prerequisites | Dependencies and things that have to be done in before | Product Session, Refinement, TechSpec |
| Acceptance Criteria | How to prove that the user story is implemented. | Product Session, Refinement |
| Tech Spec | What to do to fulfill the user story. | TechSpec and Estimation |
| Estimation | How long will it take. How much effort is needed. Costs. | TechSpec and Estimation |
Definition of Ready
- User Story finalised
- User Story commissioned
Definition of Done
- User Story passed QA on staging
Release Checklist
Is defined here: Rollout.md
| Title | Modified |
|---|
No matching items