Development Flow
por Andrei Pirvulet
1. Release preparement
1.1. Urmarire data release story-uri.
1.2. Plan de release per story
2. Intrebari
2.1. Cine e responsabil de implementarea tehnica?
3. Tasks
3.1. Simulare 2 sprinturi
3.1.1. Now
3.1.2. TO BE
4. Story initiation
4.1. JIRA Flow
4.1.1. Lista cu subtaskuri jira si cand se folosesc
4.2. Mod de folosire JIRA, Stash, Crucible
5. Development
5.1. Code writing
5.1.1. Cum a fost scris ( Complexitate, clean code, coding standards)
5.2. Git flow
5.2.1. Respectare guideline-uri pentru branchuri, commit messages etc
5.3. Unit test writing
5.4. Verifications
5.4.1. Each project should have it's configuration files for the various tools
5.4.2. CodeSniffer
5.4.3. Mess detector
5.4.4. Respectare flux (s-a facut CR, s-a facut testare etc.)
6. Testing
6.1. Rulare teste functionale - mandatory
6.2. Scriere teste functionale - mandatory
6.3. Plan de testare scris in avans ( recomandat inainte de start sprint ) - Analizam in functie de fluxul de pregatire story-uri
6.4. Review
6.4.1. Done by PO, end users etc.
6.4.2. Ramane la Sprint Review