Templates 
Software Development
Software Development
Software Development
This is a typical software development process of releasing a new feature. The Product Owner will define a new feature and the Develompent team will work on it and release it.
Software Development
This diagram was created on Jan 14, 2021 4:31 PM and was last updated Mar 8, 2021 9:36 AM.
1.
Define New Feature
Define New Feature
Work with the client or stakeholder to create scope, requirements and deadlines.
Links to2. Implement Feature
2.
Implement Feature
Implement Feature
Should go back and forth with Product Owner if technical requirements are unclear or confusing. Generally extremely important to leave developer alone and undisturbed during this time. May react poorly if startled with moving deadlines or changing requirements.
Linked from13. Find Bugand 1 more
Links to4. Complete Developmentand 1 more
3.
Build Automation Tests for New Feature
Build Automation Tests for New Feature
QA should report back to development if they find any bugs immediately so they get a head start. Needs to be documented as well.
Linked from2. Implement Feature
Links to4. Complete Development
4.
Complete Development
Complete Development
Feature should work as expected.
Linked from2. Implement Featureand 1 more
Links to5. Code Review
5.
Code Review
Code Review
Important to review testing results as well as main code.
Linked from4. Complete Developmentand 1 more
Links to6. Is Code Acceptable?
6.
Is Code Acceptable?
Is Code Acceptable?
Has the code been reviewed and is it acceptable to go live?
Linked from5. Code Review
Links to7. Commit Hook/Trigger build
7.
Commit Hook/Trigger build
Commit Hook/Trigger build
Important for developers to check up on this immediately after build.
Linked from6. Is Code Acceptable?
Links to9. Pass the Acceptance Test?
8.
Refactor Code
Refactor Code
Important for developer to communicate with lead developer during this process to negate unnecessary acceptance test failures.
Linked from6. Is Code Acceptable?and 1 more
Links to5. Code Review
9.
Pass the Acceptance Test?
Pass the Acceptance Test?
Has the code passed the acceptance test?
Linked from7. Commit Hook/Trigger build
Links to10. Push to Staging
10.
Push to Staging
Push to Staging
Important for developers to check up on this immediately after build.
Linked from9. Pass the Acceptance Test?
Links to11. Test the Staging Build
11.
Test the Staging Build
Test the Staging Build
The QA Specialist will test the build on the Staging environment.
Linked from10. Push to Staging
12.
Passes Automated E2E & Non Functional Tests?
Passes Automated E2E & Non Functional Tests?
Does the code pass the automated end-to-end tests and non-functional testing?
Linked from11. Test the Staging Build
Links to14. QA Analysis Documentation
14.
QA Analysis Documentation
QA Analysis Documentation
Please use given template to create documentation.
Links to15. Release New Version
15.
Release New Version
Release New Version
Product Owner needs to publish write up on new versions.
Linked from14. QA Analysis Documentation
