Development Workflow: Difference between revisions

From Bloomex Wiki
Jump to navigation Jump to search
No edit summary
No edit summary
Line 3: Line 3:


{| class="wikitable"
{| class="wikitable"
|+ Regular Ticket
|+
|-
|-
! Steps !! Header text !! Header text
! colspan="5" |Development Workflow
|-
|-
| 1. Creating ||  ←
| colspan="5" |Regular Ticket
 
|-
<span style="font-size:200%;color:#FF0000;">↑</span>
|'''Steps'''|| colspan="2" |'''Role & Status'''
 
|'''Assignee'''
→↓
| '''Description'''
|-
| rowspan="2" |1. '''Creating'''
| colspan="2" |Author
|
|
|-
|'''→'''||'''''New'''''
|IT Development
|Writing a Task and Description in Redmine for IT Development
|-
| rowspan="6" |2. '''Analyzing'''|| colspan="2" |Project Manager (PM)
|
|
|-
|<span style="font-size:200%;color:#FF0000;">↑</span>
|Analyzing
|Author
|
|-
|'''→'''
|Analyzing
|PM (if on analyzing)
|
|-
|'''→'''
|Paused
|PM (if on pause)
|
|-
|'''→'''
|Queue
|PM (if in line)
|
|-
|'''↓'''
|'''''Development'''''
|Developer name
|
|-
| rowspan="11" |3. '''Development'''
| colspan="2" |Developer
|
|
|-
|<span style="font-size:200%;color:#FF0000;">↑</span>
|'''''PM Analyzing'''''
|PM
|
|-
|'''→'''
|In progress
|Developer name (if on development)
|
|-
|'''→'''
|Development is suspended
|Developer name (if on pause)
|
|-
|'''↓'''
|'''''Code review'''''
|Senior Developer
|
|-
| colspan="2" |Senior Developer
|
|
|-
|<span style="font-size:200%;color:#FF0000;">↑</span>
|'''''Rework'''''
|Developer name
|
|-
|'''→'''
|In reviewing
|if need time
|
|-
|'''↓'''
|'''''Move to Dev'''''
|Developer name
|
|-
| colspan="2" |Developer
   
|
|
|-
|'''↓'''
|'''''Test Dev'''''
|QA
|
|-
|4. '''Testing on Dev'''
| colspan="2" |Quality Assurance (QA)
|
|
|-
|
|<span style="font-size:200%;color:#FF0000;">↑</span>
|'''''Rework'''''
|Developer name
|
|-
|
|'''→'''
|In testing
|Tester name (if on testing)
|
|-
|
|'''→'''
|Testing queue
|QA (if in line)
|
|-
|???
|'''↓'''
|Test Dev (if need)
|Author
|
|-
|
|'''↓'''
|Testing has been completed
|QA
|
|-
|
| colspan="2" |Author (optional)
|
|
|-
|
|<span style="font-size:200%;color:#FF0000;">↑</span>
|'''''Rework'''''
|QA
|
|-
|
|'''↓'''
|Testing has been completed
|QA
|
|-
|
|'''↓'''
|'''''Move to Stage'''''
|Developer name
|
|-
|
| colspan="2" |Developer
|
|
|-
|
|'''↓'''
|'''''Test Stage'''''
|QA
|
|-
| rowspan="5" |5. '''Testing on Stage'''
| colspan="2" |Quality Assurance (QA)
|
|
|-
|<span style="font-size:200%;color:#FF0000;">↑</span>
|'''''Rework'''''
|Developer name
|
|-
|'''→'''
|In testing
|Tester name (if on testing)
|
|-
|'''→'''
|Testing queue
|QA (if in line)
|
|-
|'''↓'''
|Ready to Install
|QA
|
|-
| colspan="5" |'''Go to Release-Ticket process'''
|-
| rowspan="2" |6. '''Release'''
| colspan="2" |Quality Assurance (QA)
|
|
|-
|'''↓'''
|Test Live
|QA
|
|-
| rowspan="14" |7. '''Testing on Live'''
| colspan="2" |Quality Assurance (QA)
|
|
|-
|<span style="font-size:200%;color:#FF0000;">↑</span>
|'''''Rework'''''
|PM
|
|-
|'''→'''
|In testing
|Tester name (if on testing)
|
|-
|
|Test Live
|Author
|
|-
| colspan="2" |Author
|
|
|-
|<span style="font-size:200%;color:#FF0000;">↑</span>
|'''''Rework'''''
|QA
|
|-
|'''↓'''
|'''''Completed'''''
|QA
|
|-
| colspan="2" |Quality Assurance (QA)
|
|
|-
|'''→'''
|Paused
|QA (preparing to Close)
|
|-
|X
|Closed
|
|
|-
| colspan="2" |Project Manager (PM)
|
|
|-
|<span style="font-size:200%;color:#FF0000;">↑</span>
|'''''Rework'''''
|Developer name (if Hotfix)
|
|-
|-
| 2. Analyze || Example || Example
| colspan="2" |if need rollback go to Release Ticket
(to step 3)
|
|
|-
|-
| Example || Example || Example
|X
|Closed
|
|create a new ticket (if needed)
|}
|}


=New-Release-Ticket=
=New-Release-Ticket=
{| class="wikitable"
|+
! colspan="5" |New-Release-Ticket
|-
|'''Steps'''
| colspan="2" |'''Role & Status'''
|'''Assignee'''
|'''Description'''
|-
| rowspan="3" |1. '''Creating ('''QA creates the ticket)
| colspan="2" |Quality Assurance (QA)
|
|
|-
|'''→'''
|In Progress
|QA
|
|-
|'''↓'''
|'''''Ready to Install'''''
|System Administration
|
|-
| rowspan="13" |2. '''Release'''
| colspan="2" |System Administrator
|
|
|-
|'''→'''
|Planning and Install
|System Administration
|
|-
|'''↓'''
|'''''Test Live'''''
|QA
|
|-
| colspan="2" |Quality Assurance (QA)
|
|
|-
|<span style="font-size:200%;color:#FF0000;">↑</span>
|'''''Rework'''''
|PM
|
|-
|'''→'''
|In testing
|QA
|
|-
|X
|Closed
|
|
|-
| colspan="2" |Project Manager (PM)
|
|
|-
|<span style="font-size:200%;color:#FF0000;">↑</span>
|Rollback
|System Administration
|
|-
| colspan="2" |System Administrator
|
|
|-
|'''↓'''
|Rollback completed
|QA
|
|-
| colspan="2" |Quality Assurance (QA)
|
|
|-
|'''→'''
|In Progress
|QA
|
|}

Revision as of 19:21, 24 August 2023


Development Workflow
Regular Ticket
Steps Role & Status Assignee Description
1. Creating Author
→ New IT Development Writing a Task and Description in Redmine for IT Development
2. Analyzing Project Manager (PM)
↑ Analyzing Author
→ Analyzing PM (if on analyzing)
→ Paused PM (if on pause)
→ Queue PM (if in line)
↓ Development Developer name
3. Development Developer
↑ PM Analyzing PM
→ In progress Developer name (if on development)
→ Development is suspended Developer name (if on pause)
↓ Code review Senior Developer
Senior Developer
↑ Rework Developer name
→ In reviewing if need time
↓ Move to Dev Developer name
Developer
↓ Test Dev QA
4. Testing on Dev Quality Assurance (QA)
↑ Rework Developer name
→ In testing Tester name (if on testing)
→ Testing queue QA (if in line)
??? ↓ Test Dev (if need) Author
↓ Testing has been completed QA
Author (optional)
↑ Rework QA
↓ Testing has been completed QA
↓ Move to Stage Developer name
Developer
↓ Test Stage QA
5. Testing on Stage Quality Assurance (QA)
↑ Rework Developer name
→ In testing Tester name (if on testing)
→ Testing queue QA (if in line)
↓ Ready to Install QA
Go to Release-Ticket process
6. Release Quality Assurance (QA)
↓ Test Live QA
7. Testing on Live Quality Assurance (QA)
↑ Rework PM
→ In testing Tester name (if on testing)
Test Live Author
Author
↑ Rework QA
↓ Completed QA
Quality Assurance (QA)
→ Paused QA (preparing to Close)
X Closed
Project Manager (PM)
↑ Rework Developer name (if Hotfix)
if need rollback go to Release Ticket

(to step 3)

X Closed create a new ticket (if needed)

New-Release-Ticket

New-Release-Ticket
Steps Role & Status Assignee Description
1. Creating (QA creates the ticket) Quality Assurance (QA)
→ In Progress QA
↓ Ready to Install System Administration
2. Release System Administrator
→ Planning and Install System Administration
↓ Test Live QA
Quality Assurance (QA)
↑ Rework PM
→ In testing QA
X Closed
Project Manager (PM)
↑ Rollback System Administration
System Administrator
↓ Rollback completed QA
Quality Assurance (QA)
→ In Progress QA
Retrieved from "https://wiki.necs.ca/index.php?title=Development_Workflow&oldid=2486"