The following flow chart illustrates the Software sub-team's software development life cycle (SDLC)

Comments

• The member working on the task is responsible for pinning reviewers once changes are addressed. Reviewers will not know if changes are addressed until then.
• If code can’t be easily unit-tested unless it heavily relies on hardware, it can probably be structured differently to allow it to be more easily unit-tested.
• Members are responsible for notifying Software Leads if they cannot work on their task for long periods