Scrum in Agile:
a thread...
(Part-4/4)
a thread...
(Part-4/4)
To read the previous thread in the series, please check out the third part:
What is Scrum?
In Scrum,
We follow the waterfall approach in small iterations called sprints, commonly sprint is of two weeks.
We deliver "workable functionalities" of software at the end of each sprint.
In Scrum,
We follow the waterfall approach in small iterations called sprints, commonly sprint is of two weeks.
We deliver "workable functionalities" of software at the end of each sprint.
Clients' requirements are documented in the form of Epic/User Stories.
They can be further divided into tasks, and subtasks by keeping sprint duration in mind.
They can be further divided into tasks, and subtasks by keeping sprint duration in mind.
There is no such defined role in the team, everybody is a leader. Everybody is responsible for anything and everything.
Roles are blurred, based on the situation anyone can be given any responsibility based on their capability.
There's only one goal - "The Team Goal".
Roles are blurred, based on the situation anyone can be given any responsibility based on their capability.
There's only one goal - "The Team Goal".
Sprint can be of 1 week up to 4 weeks, commonly it is of 2 weeks.
In Sprint, the actual development takes place along with QA testing.
In Sprint, the actual development takes place along with QA testing.
At the end of the sprint, we demonstrate our work to the product owner/customer and deploy it to the client's end.
During the Sprint, there are several meetings take place.
During the Sprint, there are several meetings take place.
Meetings in Sprint:
1. Sprint Planning
2. Daily Standup
3. Sprint Review
4. Sprint Retrospection
5. Backlog Refinement
1. Sprint Planning
2. Daily Standup
3. Sprint Review
4. Sprint Retrospection
5. Backlog Refinement
"But why there're so many meetings"?
Agile focuses on open communication, face to face interaction where team can share their problem and get quick solution.
Let's see in details each meetings happen in Sprint.
Agile focuses on open communication, face to face interaction where team can share their problem and get quick solution.
Let's see in details each meetings happen in Sprint.
Sprint Planning:
Before starting the sprint, team picks the task from the backlog, estimate them as per the spring duration, and start allocating the task to the team members.
It usually takes around 1.5h-2h, depending on your team size and sprint duration.
Before starting the sprint, team picks the task from the backlog, estimate them as per the spring duration, and start allocating the task to the team members.
It usually takes around 1.5h-2h, depending on your team size and sprint duration.
Stand up Meetings:
Daily 15-25 mins of time spent on standup meetings, here team members share three important things:
1. What they did yesterday?
2. What's their today's plan?
3. Is there any blocker?
It should be as short and quick as possible.
Daily 15-25 mins of time spent on standup meetings, here team members share three important things:
1. What they did yesterday?
2. What's their today's plan?
3. Is there any blocker?
It should be as short and quick as possible.
Sprint Review:
Happens at the end of the sprint,
Where the team demonstrate the work to the client or product owner, takes feedback, and if there is major feedback given then covers them in the next sprint.
Should take approx. 45m-1h based on the no. of tasks done.
Happens at the end of the sprint,
Where the team demonstrate the work to the client or product owner, takes feedback, and if there is major feedback given then covers them in the next sprint.
Should take approx. 45m-1h based on the no. of tasks done.
Sprint Retrospection:
Happens at the end of sprint.
It helps in improving the internal process.
Where the internal team discusses three important things:
1. What went well during the sprint?
2. What can be improved?
3. Action needed to improve it?
Should take approx. 45m-1h.
Happens at the end of sprint.
It helps in improving the internal process.
Where the internal team discusses three important things:
1. What went well during the sprint?
2. What can be improved?
3. Action needed to improve it?
Should take approx. 45m-1h.
Scrum Team Size:
The ideal Scrum team size should be 7-9 members including Developers, Product Owners & Scrum Masters.
What to do if you've more members?
Divide them into Multiple Scrum Teams based on project modules.
The ideal Scrum team size should be 7-9 members including Developers, Product Owners & Scrum Masters.
What to do if you've more members?
Divide them into Multiple Scrum Teams based on project modules.
Different Roles in a Scrum Team:
1. Developer
2. Scrum Master
3. Product Owner
1. Developer
2. Scrum Master
3. Product Owner
Developer:
It includes everybody who is responsible for developing the software not only coders.
It includes UI/UX Designers, Developers, DBAs, DevOps, QA, etc.
The development team is mostly self-organized where everybody knows their job well.
It includes everybody who is responsible for developing the software not only coders.
It includes UI/UX Designers, Developers, DBAs, DevOps, QA, etc.
The development team is mostly self-organized where everybody knows their job well.
Scrum Master:
Scrum Master conducts different meetings in Scrum.
Acts as a buffer between development team and the external world.
Scrum master monitors the development team's progress and makes sure the team is self-sufficient.
Scrum Master conducts different meetings in Scrum.
Acts as a buffer between development team and the external world.
Scrum master monitors the development team's progress and makes sure the team is self-sufficient.
Product Owner:
The product owner represents customers' interests.
Takes final decision on the product.
Responsible for clearing all the hurdles for the team.
Makes sure the Scrum team performs all the necessary processes for the betterment of the product.
The product owner represents customers' interests.
Takes final decision on the product.
Responsible for clearing all the hurdles for the team.
Makes sure the Scrum team performs all the necessary processes for the betterment of the product.
Conclusion:
Scrum is a very powerful way of dealing with client changes, where we iteratively work on a single thing until it gets perfect.
Here, change can be introduced at any phase and that's why the Scrum team needs to be more flexible in designing the solution.
Scrum is a very powerful way of dealing with client changes, where we iteratively work on a single thing until it gets perfect.
Here, change can be introduced at any phase and that's why the Scrum team needs to be more flexible in designing the solution.
That's the end of this series!
How was it?
Did you like this series?
Do you want me to make another series on your suggested topic?
Let me know in the comments below...
To read the complete series from the beginning start with this thread...
How was it?
Did you like this series?
Do you want me to make another series on your suggested topic?
Let me know in the comments below...
To read the complete series from the beginning start with this thread...
Namaste, Myself Vikas.
I write a thread every Mon, Wed & Fri on
Java, Javascript & Fullstack Development.
To read all my future threads follow @vikasrajputin
Till then, take care.
Keep Learning and Keep Growing!
I write a thread every Mon, Wed & Fri on
Java, Javascript & Fullstack Development.
To read all my future threads follow @vikasrajputin
Till then, take care.
Keep Learning and Keep Growing!
جاري تحميل الاقتراحات...