Software Engineering Process - SeedCompany/cord-docs GitHub Wiki
Refining
- The Tech Lead is responsible for ensuring the story is well refined with help/participant from other engineers.
- The Tech Lead is responsible for moving stories from Refining to Grooming when they agree with Product that it is ready.
- A story is done with refinement when
- all necessary Dev Tasks have been created
- the requirements doc has the necessary information to understand what is needed and a general direction of how we will implement
- any engineer who has been onboarded to the repo could look at the story and would be clear with what they need to do to start work
- It is the Tech Leads responsibility to identify when Carson’s input is needed as part of Refining and to gather that input.
Grooming
- The Tech Lead is responsible for ensuring a story is groomed
- The Product Squad is responsible for participating in story grooming
- A well-groomed story
- has a shared understanding among squad members
- has been moved from Refining to Grooming by the Tech Lead
- has all additional information added to it that was identified in the Grooming conversations
- has story points if it is not a bug or a spike
- The Tech Lead is responsible for moving a story from Grooming to Ready to Start after Grooming is complete
Ready to Start
- Before a story is started, the developer confirms with the Tech Lead/Carson about the Tech design/details. Solid architecture solution
needs to be confirmed before the story is started.
- Will & Andre reach to seniors for their ideas, go to to Carson after that
- Brent/Bryan consult with each other and go to Carson
- Andrew/Rob consult with each other and go to Carson
- When the story has 1/4 or 1/3 finished, the developers do another check for the current and future work
- Depends on the complexity of the story, there could be another check before the PR is raised.
PR Reviews
- 2 reviewers are required to approve and merge
- Final review
- Tech Lead or Carson can be the final reviewer
- PR review requestor should take the ownership of adding coding standard related to their PRs to the Coding Standards documentation if the standard is not stated at the document.
Monday Tickets Status Diagram and Readiness Process
The Monday Status Workflow and Description outlines the Monday Ticket Status and Workflow. It also details the expectations and responsibilities of various parties based on the different ticket statuses.
Weekly Meeting Schedule
- M-F: Daily virtual Standup Meeting
- Monday: 10-11am DSU and Software Development Team Meeting
- Tuesday: 10-12am Cord Squad Meeting (connect, refining, grooming)
- Wednesday
- Sprint Week: 10-11am (connect, Sprint Planning/Retro)
- Mid-Sprint Week: 10-10:30am (connect)?
- Thursday: 10-11:30am Rogue Squad Meeting