Scrum

There are few Scrum-specific details that should be adhered to in regards to the Sprint.

Sprints will be 2 weeks long (by default). This time period allows for sufficiently small tickets and exposes problems early. Under certain circumstances, 1 or 3 week Sprints can be used, however, it is best to stick to 2 weeks.
- 1 Week - This should only be used for small teams on small projects that have short timelines and will iterate very quickly.
- 3 Week - This should only be used for experienced teams that have proven delivery history and are on large projects. When 3 week Sprints are used, QA should be considered part of the 3 weeks. In other words, tickets should be small enough so that QA can complete the work within the same Sprint as the development.
Stand-ups will happen daily (90% of the time). Sometimes small projects require less touch and meeting less than 5 days a week is acceptable. For example, a lone part-time engineer working with a lone part-time QA can meet 2-3 time a week.
- During the Stand-Up, four questions needs to be answered.
  - “What did I do yesterday?”
  - “What am I going to do today?”
  - “What is the status of the tickets assigned to me?”
  - “Is there anything blocking me from completed my tickets before the end of the Sprint” - It is the responsibility of the Project Manager to help move blockers out of the engineer’s way.

Review this page for ticket type information
All work must be accompanied by a scored ticket that has a description of the task. Quality Assurance will use this description (and the linked Story) to determine if the task is complete and correct.
- Quality Assurance will have their own Tasks) that relate to the Developer Tasks. The QA tickets should “block” the Developer Task.

Ticket estimate will be done using a modified Fibonacci sequence for sizing 0, 1, 2, 3, 5, 8, 13, 20, 40, 100
- The ticket size for a development Task should include:
  - Research/analysis
  - Development
  - Unit test writing
  - Code reviews
- Quality Assurance creates their own tickets and sizes them based on the development or story ticket
- If a ticket is larger than a single Sprint, then break it down into multiple Tasks
- Every ticket size must be less than the total number of points that a person can accomplish per Sprint. There are no exceptions. If the ticket needs to be smaller, then break is down into multiple Tasks
Use 12-15 points per Sprint per person for full-time engineers (less for part time engineers). This allows for enough granularity in the sizing of the tickets.
Ticket sizing will be done during the kick-off meeting (but can be done ahead of time, too).

Related