Introduction
This document collects the information I have learnt from my software (web) development experience in the past.
Since we have not sticky followed specific methdology like Scrum or Kaban, the following information is just a summary, not a guideline or learning material for others.
Reference Articles
- Kanban - A brief introduction | Atlassian
- Agile Workflow: What It Is & How To Implement One | Hive
- 华为云工作项中新建工作项的Epic、Feature、Story和Task分别都是做什么的-云社区-华为云 (huaweicloud.com)
- What Are The Differences Between An Epic, Story, Task And Feature? (goretro.ai)
- UI/UX Design Deliverables Checklist - MobiDev
Different dimension
| Dimension | Description |
|---|---|
| Stages | The software development can be divided into different stages, time-sensitive |
| Types | The type of work. For example: Epic, Feature, User Story, Task, Bug,...etc. |
| Roles | The worker in specific role |
Stages
The following are the different stages in the Agile SDLC
Initial Stage
A staring point initiated (and owned):
- By the stakeholders, business analyst, product manager, for Project vision or Business idea (e.g. Epic, Feature, User Story)
- By internal needs (e.g. Request or Task)
- By bug reporting
Planning Stage
By busines analyst or product manager, and/or project manager:
- High-level user requirements or scope
- Ballpark estimation of the resource, cost,...etc.
- Rough schedule
By technical:
- Ballpark estimation of the time needed
- Technical feasibility study
By creative:
- Ballpark estimation of the time needed
- UI/UX Research
- Brief
- User Personas
- Screen Sections Scheme (custom deliverables)
- User Behavior Diagram (custom deliverables)
By QA:
- Ballpark estimation of the time needed (per the complete test cycle)
Hands-on Working Stage
In general, it is called implementation stage. However, it can be better to express and highlight the non-IT work using the Hands-on work. The hands-on work includes:
(Italic = Optional / If needed)
By busines analyst or product manager:
- User/interact flows
- Information architecture / Sitemap
- User requirements
- User stories
- Release plan
By creative:
- Sketching
- Wireframing
- Visualization
- Media assets creation
- Visual QA
By technical:
- User requirement and System analysis
- POC
- Technical and System design
- Software design
- Data modeling
- API design
- Coding and testing (e.g. unit test)
- Integration and testing
- Data and/or System Migration
- Sampling Test (Functional/Regression/API)
- Deployment (and fallback) plan
By QA:
- Test cases
- Testing Plan
Testing Stage
(Italic = Optional / If needed)
By QA:
- Funtional Test
- Regression Test
- API Test
- Data/Text checking
By busines analyst, product manager, or project manager:
- Sampling test (Functional/Regression)
- Selective Data/Text checking
By creative:
- Visual (or media, including UI text) checking
By technical:
- Deployment (to staging)
- System integration/migration test
- Data migration test
- Security check
- Stress test
By user:
- Conduct UAT
Release Stage
(Italic = Optional / If needed)
By QA:
- Sampling test (Functional/Regression) with production data
By busines analyst, product manager, or project manager:
- Sampling test (Functional/Regression) with production data
- Selective Data/Text checking
By creative:
- Sampling visual (or media, including UI text) checking
By technical:
- Deployment (to production)
- Security scaning
By user:
- Final check
The workflow I used in the company in 2022
