Development Workflow: Difference between revisions

From Bloomex Wiki
Jump to navigation Jump to search
No edit summary
No edit summary
 
(17 intermediate revisions by 2 users not shown)
Line 1: Line 1:
 
__TOC__
 
=Workflow=
 
==Regular Ticket==
{| class="wikitable"
{| class="wikitable"
|+
|+
Line 11: Line 11:
|'''Steps'''|| colspan="2" |'''Role & Status'''
|'''Steps'''|| colspan="2" |'''Role & Status'''
|'''Assignee'''
|'''Assignee'''
| '''Description'''
| '''Description'''  
|-
|-
| rowspan="2" |1. '''Creating'''
| rowspan="2" |1. '''Creating'''
Line 22: Line 22:
|Writing a Task and Description in Redmine for IT Development
|Writing a Task and Description in Redmine for IT Development
|-
|-
| rowspan="6" |2. '''Analyzing'''|| colspan="2" |Project Manager (PM)
| rowspan="7" |2. '''Analyzing'''|| colspan="2" |Project Manager (PM)
|
|
|
|
|-
|-
|<span style="font-size:200%;color:#FF0000;">↑</span>
|<span style="font-size:100%;color:#FF0000;">↑</span>
|Analyzing
|Analyzing
|Author
|Author
Line 34: Line 34:
|Analyzing
|Analyzing
|PM (if on analyzing)
|PM (if on analyzing)
|
|Analyzing of the task and writing Terms of Reference and Test Planning (if needed)
|-
|-
|'''→'''
|'''→'''
|Paused
|Paused
|PM (if on pause)
|PM (if on pause)
|
|During the analyzing, a decision was made that this ticket is not relevant at the moment or this ticket can't be developed at the moment
|-
|-
|'''→'''
|'''→'''
Line 45: Line 45:
|PM (if in line)
|PM (if in line)
|
|
|-
|x
|Rejected
|
|If the ticket was created as a duplicate or during the analyzing it was decided to reject this ticket
|-
|-
|'''↓'''
|'''↓'''
|'''''Development'''''
|'''''Development'''''
|Developer name
|Developer name
|
|Preparing the application and developer priority (Give the application Development Priority A, B, C, or D). A maximum of 3 category A tickets can be assigned to a developer at the same time
|-
|-
| rowspan="11" |3. '''Development'''
| rowspan="11" |3. '''Development'''
Line 56: Line 61:
|
|
|-
|-
|<span style="font-size:200%;color:#FF0000;">↑</span>
|<span style="font-size:100%;color:#FF0000;">↑</span>
|'''''PM Analyzing'''''
|'''''PM Analyzing'''''
|PM
|PM
Line 68: Line 73:
|'''→'''
|'''→'''
|Development is suspended
|Development is suspended
|Developer name (if on pause)
|Developer name (if on pause or in line)
|
|If the developer received an urgent ticket or a Hotfix, then the ticket should be moved to this status
|-
|-
|'''↓'''
|'''↓'''
|'''''Code review'''''
|'''''Code review'''''
|Senior Developer
|Senior-Developer name
|
|Write a link to the merge-request in the ticket
|-
|-
| colspan="2" |Senior Developer
| colspan="2" |Senior Developer
Line 80: Line 85:
|
|
|-
|-
|<span style="font-size:200%;color:#FF0000;">↑</span>
|<span style="font-size:100%;color:#FF0000;">↑</span>
|'''''Rework'''''
|'''''Rework'''''
|Developer name
|Developer name
|
|Write a comment in the ticket
|-
|-
|'''→'''
|'''→'''
Line 93: Line 98:
|'''''Move to Dev'''''
|'''''Move to Dev'''''
|Developer name
|Developer name
|
|Aprove to Dev
|-
|-
| colspan="2" |Developer
| colspan="2" |Developer
Line 103: Line 108:
|'''''Test Dev'''''
|'''''Test Dev'''''
|QA
|QA
|
|Merge to Dev
|-
|-
|4. '''Testing on Dev'''
|4. '''Testing on Dev'''
Line 111: Line 116:
|-
|-
|
|
|<span style="font-size:200%;color:#FF0000;">↑</span>
|<span style="font-size:100%;color:#FF0000;">↑</span>
|'''''Rework'''''
|'''''Rework'''''
|Developer name
|Developer name
Line 120: Line 125:
|In testing
|In testing
|Tester name (if on testing)
|Tester name (if on testing)
|
|When a ticket is on testing, the QA assigns this ticket to himself. Write the test result in a comment.
|-
|-
|
|
Line 128: Line 133:
|
|
|-
|-
|???
|
|'''↓'''
|'''↓'''
|Test Dev (if need)
|Test Dev (if needed)
|Author
|Author (if needed)
|
|If necessary, assignee the ticket to the Author for feedback
|-
|-
|
|
|'''↓'''
|'''→'''
|Testing has been completed
|Testing has been completed (optional)
|QA
|QA
|
|
|-
|-
|
|
| colspan="2" |Author (optional)
| colspan="2" |Author (if needed)
|
|
|
|
|-
|-
|
|
|<span style="font-size:200%;color:#FF0000;">↑</span>
|<span style="font-size:100%;color:#FF0000;">↑</span>
|'''''Rework'''''
|'''''Rework'''''
|QA
|QA
Line 155: Line 160:
|Testing has been completed
|Testing has been completed
|QA
|QA
|If everything is ok and the conditions of the ticket are done. Aprove to Stage
|-
|
| colspan="2" |Quality Assurance (QA)
|
|
|
|-
|-
Line 161: Line 171:
|'''''Move to Stage'''''
|'''''Move to Stage'''''
|Developer name
|Developer name
|
|Aprove to Stage
|-
|-
|
|
Line 172: Line 182:
|'''''Test Stage'''''
|'''''Test Stage'''''
|QA
|QA
|
|Merge to Stage
|-
|-
| rowspan="5" |5. '''Testing on Stage'''
|5. '''Testing on Stage'''
| colspan="2" |Quality Assurance (QA)
| colspan="2" |Quality Assurance (QA)
|
|
|
|
|-
|-
|<span style="font-size:200%;color:#FF0000;">↑</span>
|
|<span style="font-size:100%;color:#FF0000;">↑</span>
|'''''Rework'''''
|'''''Rework'''''
|Developer name
|Developer name
|
|
|-
|-
|
|'''→'''
|'''→'''
|In testing
|In testing
Line 189: Line 201:
|
|
|-
|-
|
|'''→'''
|'''→'''
|Testing queue
|Testing queue
Line 194: Line 207:
|
|
|-
|-
|
|'''↓'''
|'''↓'''
|Ready to Install
|Ready to Install
Line 201: Line 215:
| colspan="5" |'''Go to Release-Ticket process'''
| colspan="5" |'''Go to Release-Ticket process'''
|-
|-
| rowspan="2" |6. '''Release'''
|6. '''Release'''
| colspan="2" |Quality Assurance (QA)
| colspan="2" |Quality Assurance (QA)
|
|
|
|
|-
|-
|
|'''↓'''
|'''↓'''
|Test Live
|'''''Test Live'''''
|QA
|QA
|
|
|-
|-
| rowspan="14" |7. '''Testing on Live'''
| rowspan="15" |7. '''Testing on Live'''
| colspan="2" |Quality Assurance (QA)
| colspan="2" |Quality Assurance (QA)
|
|
|
|
|-
|-
|<span style="font-size:200%;color:#FF0000;">↑</span>
|<span style="font-size:100%;color:#FF0000;">↑</span>
|'''''Rework'''''
|'''''Rework'''''
|PM
|PM
Line 226: Line 241:
|
|
|-
|-
|'''→'''
|Testing queue
|QA (if in line)
|
|
|Test Live
|-
|'''→'''
|Test Live (if needed)
|Author
|Author
|
|
|-
|-
| colspan="2" |Author
| colspan="2" |Author (if needed)
|
|
|
|
|-
|-
|<span style="font-size:200%;color:#FF0000;">↑</span>
|<span style="font-size:100%;color:#FF0000;">↑</span>
|'''''Rework'''''
|'''''Rework'''''
|QA
|QA
Line 249: Line 269:
|
|
|-
|-
|'''→'''
|'''↓'''
|Paused
|Completed on Live
|QA (preparing to Close)
|QA (preparing to Close)
|
|Transfer to Issue is completed status if there are no bugs and errors
|-
|-
|X
|X
Line 263: Line 283:
|
|
|-
|-
|<span style="font-size:200%;color:#FF0000;">↑</span>
|<span style="font-size:100%;color:#FF0000;">↑</span>
|'''''Rework'''''
|'''''Rework'''''
|Developer name (if Hotfix)
|Developer name (if Hotfix)
|
|Analysing Feedback and sending to Developer for Hotfix. Adding Rollback Request  to Release-Ticket.
|-
|-
| colspan="2" |if need rollback go to Release Ticket
| colspan="2" |if needed rollback go to Release Ticket
(to step 3)
(to step 3)
|
|
Line 279: Line 299:
|}
|}


=New-Release-Ticket=
==New-Release-Ticket==
{| class="wikitable"
{| class="wikitable"
|+
|+
Line 289: Line 309:
|'''Description'''
|'''Description'''
|-
|-
| rowspan="3" |1. '''Creating ('''QA creates the ticket)
| rowspan="3" |1. '''Creating''' (QA creates the ticket)
| colspan="2" |Quality Assurance (QA)
| colspan="2" |Quality Assurance (QA)
|
|
Line 297: Line 317:
|In Progress
|In Progress
|QA
|QA
|
|The tester completes a Release-Ticket and adds to this ticket other tickets that have been tested on the Stage
|-
|-
|'''↓'''
|'''↓'''
|'''''Ready to Install'''''
|'''''Ready to Install'''''
|System Administration
|System Administration
|
|The Release-Ticket is ready to be uploaded to Life
|-
|-
| rowspan="13" |2. '''Release'''
| rowspan="13" |2. '''Release'''
Line 312: Line 332:
|Planning and Install
|Planning and Install
|System Administration
|System Administration
|
|Planning time for Release is every Thursday 1pm EST
|-
|-
|'''↓'''
|'''↓'''
|'''''Test Live'''''
|'''''Test Live'''''
|QA
|QA
|
|Merge to Live
|-
|-
| colspan="2" |Quality Assurance (QA)
| colspan="2" |Quality Assurance (QA)
|
|
|
|Responsible tester for Release moves all tickets from Release-Ticket to Test Live status
|-
|-
|<span style="font-size:200%;color:#FF0000;">↑</span>
|<span style="font-size:100%;color:#FF0000;">↑</span>
|'''''Rework'''''
|'''''Rework'''''
|PM
|PM
|
|If a Release-Tcket needs to be Rolledback
|-
|-
|'''→'''
|'''→'''
|In testing
|In testing
|QA
|QA
|
|Choose Responsible person who’ll test and close Release-Ticket
|-
|-
|X
|X
Line 342: Line 362:
|
|
|-
|-
|<span style="font-size:200%;color:#FF0000;">↑</span>
|<span style="font-size:100%;color:#FF0000;">↑</span>
|Rollback
|'''''Rollback'''''
|System Administration
|System Administration
|
|In case we need a Rollback, write a request and send a message to IT Helpdesk (if needed)
|-
|-
| colspan="2" |System Administrator
| colspan="2" |System Administrator
Line 352: Line 372:
|-
|-
|'''↓'''
|'''↓'''
|Rollback completed
|'''''Rollback completed'''''
|QA
|QA
|
|
Line 363: Line 383:
|In Progress
|In Progress
|QA
|QA
|
|The tester again completes a Release-Ticket and adds to this ticket other tickets that have been tested on the Stage
|}
|}
'''<big>If errors are found at any of the steps, change the status and Assignee as Workflow recommend</big>'''
<big>'''If the task requires additional materials such as design or other, the Project Manager (PM) creates a Subtask'''</big>
'''<big>Execution of tasks without a ticket is <u>not allowed</u></big>'''<u>.</u>
'''<big>In case of critical errors, it is allowed to formulate the problem in a different way.</big>'''
'''<big>When creating duplicate tickets, these tickets will be closed.</big>'''
'''<big>When changing Assignee, comments are written about what was done: NECESSARILY</big>'''
=Development Workflow Instructions=
[[Instructions to the Author]]
[[Instructions to the Developer]]
[[Instructions to the Quality Assurance]]
[[Instructions to the Project Manager]]
[[Instructions to the System Administrator]]

Latest revision as of 18:22, 18 September 2023

Workflow

Regular Ticket

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) Analyzing of the task and writing Terms of Reference and Test Planning (if needed)
→ Paused PM (if on pause) During the analyzing, a decision was made that this ticket is not relevant at the moment or this ticket can't be developed at the moment
→ Queue PM (if in line)
x Rejected If the ticket was created as a duplicate or during the analyzing it was decided to reject this ticket
↓ Development Developer name Preparing the application and developer priority (Give the application Development Priority A, B, C, or D). A maximum of 3 category A tickets can be assigned to a developer at the same time
3. Development Developer
↑ PM Analyzing PM
→ In progress Developer name (if on development)
→ Development is suspended Developer name (if on pause or in line) If the developer received an urgent ticket or a Hotfix, then the ticket should be moved to this status
↓ Code review Senior-Developer name Write a link to the merge-request in the ticket
Senior Developer
↑ Rework Developer name Write a comment in the ticket
→ In reviewing if need time
↓ Move to Dev Developer name Aprove to Dev
Developer
↓ Test Dev QA Merge to Dev
4. Testing on Dev Quality Assurance (QA)
↑ Rework Developer name
→ In testing Tester name (if on testing) When a ticket is on testing, the QA assigns this ticket to himself. Write the test result in a comment.
→ Testing queue QA (if in line)
↓ Test Dev (if needed) Author (if needed) If necessary, assignee the ticket to the Author for feedback
→ Testing has been completed (optional) QA
Author (if needed)
↑ Rework QA
↓ Testing has been completed QA If everything is ok and the conditions of the ticket are done. Aprove to Stage
Quality Assurance (QA)
↓ Move to Stage Developer name Aprove to Stage
Developer
↓ Test Stage QA Merge to Stage
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)
→ Testing queue QA (if in line)
→ Test Live (if needed) Author
Author (if needed)
↑ Rework QA
↓ Completed QA
Quality Assurance (QA)
↓ Completed on Live QA (preparing to Close) Transfer to Issue is completed status if there are no bugs and errors
X Closed
Project Manager (PM)
↑ Rework Developer name (if Hotfix) Analysing Feedback and sending to Developer for Hotfix. Adding Rollback Request to Release-Ticket.
if needed 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 The tester completes a Release-Ticket and adds to this ticket other tickets that have been tested on the Stage
↓ Ready to Install System Administration The Release-Ticket is ready to be uploaded to Life
2. Release System Administrator
→ Planning and Install System Administration Planning time for Release is every Thursday 1pm EST
↓ Test Live QA Merge to Live
Quality Assurance (QA) Responsible tester for Release moves all tickets from Release-Ticket to Test Live status
↑ Rework PM If a Release-Tcket needs to be Rolledback
→ In testing QA Choose Responsible person who’ll test and close Release-Ticket
X Closed
Project Manager (PM)
↑ Rollback System Administration In case we need a Rollback, write a request and send a message to IT Helpdesk (if needed)
System Administrator
↓ Rollback completed QA
Quality Assurance (QA)
→ In Progress QA The tester again completes a Release-Ticket and adds to this ticket other tickets that have been tested on the Stage

If errors are found at any of the steps, change the status and Assignee as Workflow recommend

If the task requires additional materials such as design or other, the Project Manager (PM) creates a Subtask

Execution of tasks without a ticket is not allowed.

In case of critical errors, it is allowed to formulate the problem in a different way.

When creating duplicate tickets, these tickets will be closed.

When changing Assignee, comments are written about what was done: NECESSARILY

Development Workflow Instructions

Instructions to the Author

Instructions to the Developer

Instructions to the Quality Assurance

Instructions to the Project Manager

Instructions to the System Administrator

Retrieved from "https://wiki.necs.ca/index.php?title=Development_Workflow&oldid=2905"