This document discusses best practices for an agile software development lifecycle (SDLC). It defines the Definition of Ready (DOR) checklist to ensure requirements are ready for development. This includes writing user stories in a template, ensuring stories are small and independent, and clarifying all questions. It describes sprint planning meetings where the team determines which backlog items will be developed in the next sprint. On the first day of the sprint, each team member reviews assigned tickets, discusses implementation approaches, checks estimates, and tracks any open questions or dependencies.

1. Corporate AGILE & SDLC Best
Practices - Part2
(W2D2: 16Nov, 9PM)
Tausief
LinkedIn @tausiefs

2. Topic
● Definition of Ready (DOR)
● Sprint Planning Meeting
● Sprint Day1 actions

3. Definition of Ready
(DOR)
Key points
● Is the requirement ready for
development?
● If the tickets are not meeting DOR,
don’t consider them for sprint.
● Raise with the Product Owner
what all information is needed.
DOR Checklist
1. User Story written as per the template provided
2. User story is small enough
User story independent in nature
User story is estimable
1. All Assumptions are written
2. Dependencies are written
1. Devops
2. DWH
3. Architect
4. Any
3. Mocks (Are fully ready, no reworks)
4. All questions are clarified (80% minimum)
5. 3rdparty integration (if any)
1. API Documentation Attached (if necessary).
2. Credentials provided in applicable.

4. Sprint Planning
Meeting:
A sprint planning meeting is when
the team (including the Scrum
Master , Scrum Product Manager,
and Scrum Team) meets to
determine which backlog items will
be handled in the next sprint
Key items to reminder - Sprint Planning Meeting:
● Generally held on Day1 first-half of Sprint.
● But if possible try to complete it one day before
Sprint
● Majority of Grooming should finish before the
SprintPlanning Meeting.
● This meeting should be used for below
activities
○ How much stories can be picked up for
this sprint.
○ Who will work on these stories
○ And doing planning, on how UI - Server -
QA would work on these tickets.
○ If there are any open questions, again
raised.
● Expectation is full team is aware of who is
working on what tickets.

5. Sprint Day1
Day1 of Sprint is very
critical, If DONE right, it
will simplify your entire
sprint work.
Actions you should perform on Sprint Day1
● Clarity to Entire Team regarding Resource and Sprint Plan
(Who would work on which items)
● Each team member should individually go through the tickets
assigned to him/her - UI/Server/QA
○ Walkthrough all tickets of your sprint
○ Read full ticket line-by-line
○ Read earlier high-level Tech discussions (which
happened during grooming)
○ Think on low level implementation.
■ API Design, DB Design and where and how you
are planning to code.
■ Updating sub Task Details if any pending
○ Impact Analysis on existing system for functional
tickets
○ Discuss your understanding & approach with seniors.
○ Have connect UI, server, QA to be on same page
○ Double check the provided Estimate
■ And do you see, any concerns. Raise it.
○ Any open questions - track them
○ Any dependencies not answered - track them.

6. Next Actions
● Practical Implementation

7. Part 2 Ends
Tausief S
7842717511
https://www.linkedin.com/in/tausiefs/