Corporate AGILE & SDLC Best Practices - Part1 (Dec).pdf

1. Corporate AGILE & SDLC Best
Practices - Part1
(W1D4: 8Dec, 9PM)

2. Agile: Develop
project
piece-by-piece
(Not in one shot)
Multiple ways of implementing Agile
Scrum, Kanban, ScrumBan
We are focusing on Scrum
“Sprint” (2/4 weeks working window)
Roles in Agile:
● Product Owner (Acts like bridge between
Business & TechTeam)
● Scrum Master (Works with the team to
accomplish the project on time)
● Team(Seniors/Juniors/Dev-UI/Server/QA
/Devops/DBA)

3. Project Execution
From
Requirement
To
Launch
Product Owner understand the requirements from
Business, puts it into forms where TechTeam can
further start building the requirements.
● Client/Customer/Business
● => Product Owner
● => Tech Team (SM+TechTeam)
Initial steps of SDLC
1. Requirement Gathering / Grooming / Refining
2. Analysis & Design
3. Design Review
4. Coding
5. --
6. --
7. --
8. --

4. UserStory -
Business
requirement
Business requirement should be written in the form of
User-Story & added in tool like JIRA
It should follow a defined format. All of below details
should be tracked in Jira for the user-story
● 1 statement Userstory
○ As a User (Who?)
○ I Want a functionality (What?)
○ So that I can achive this benefit (Why?)
● Acceptance criteria
● Assumptions
● Dependencies
● Mockups / Wireframes
● Questions/Clarifications

5. "Requirement
Gathering /
Grooming /
Refining" Meeting
● Best practice is to keep continuously keep
refining the requirements. So work backlog is
always ready.
Checklist to consider:
● The requirements are share in the form of
UserStories
● Userstory should follow defined format
● Requirement should be written in Jira
● Product owner should get in call to explain the
requirements
● To & Fro discussions between ProductOwner &
TechTeam to finalize the requirement

6. Part 1 Ends
Tausief S
7842717511
https://www.linkedin.com/in/tausiefs/