Agile Notes
First thing I would say is need to understand the roles (Scrum master, product owner, team member) in scrum and few terms like
product backlog,
sprint backlog,
stand up meeting,
sprint planing meeting,
Retrospective meeting.
So We can say we have a complete list of items to do in future for delivery(tasks, bugs etc) That is called product backlog. Now Product owner is the person we prioritize the items which he/she wants to take first. From those items we start the sprint. For that we do sprint planning meeting.
we give story points to each task(story). Story points is kind of estimation for the task which we will take in the sprint. Now we choose the scrum master from the team, who take cares daily standup meeting. I will explain about standup. Scrum master can be any person from the team. We mostly rotate that role after every sprint.
EX:-
Assume we have 20 tasks (stories) to complete in next 2 weeks . That is a sprint and We say sprint starts. Sprint can be 2,3 weeks, but i prefer 2 weeks. there is no hard rule for that.
Now sprint has been started. Every Team membeer picks a story from the sprint ( That can be combined for 2-3 team members for a single story) and start working on that. Next day(every day) we do standup meeting. Now in standup meeting (mainly scrum master arranges that) whole scrum team will standup
together will tell only 3 things - what he/she did yesterday, what he will do today and is ther any impediments.
So the point here comes is how we see progress of stories everyday (What i did is created a board and put every story on that sticky of every story and every day we can move them on board from start-finish).
suppose, client requirement changed in between thn wht will be next step in scrum ??
yes, If you are working on some story and immediately u came to know things has been changed. That can affect only one story or whole sprint. If only one story get affected u can skip tat and start new one. Now product owner will make a task for the new stuff which came and team will pick that in next sprint as per priority.
sometimes we closes the sprint if whole flow changed and start the process again. here product owner plays a big role
the main things is once sprint start we can't add/remove any story from that..
ok documentation always helpful, but That should be minimal. What I do ask developers to write some comments on there code and documents the flow. If you have to test some feature we shold create a test strategy for that.
Agile don't oppose documentation, only support minimal and meaningful one
what is retrospective document ?
When the sprint ends we do a demo to product owner. And We do a retrospective meeting.
In that we mainly document (+ve, -ves of print) you can say what we have learnt from the sprint, what we can improve)
Like in starting days people dont understand the estimation properly the story points system.
We decide what are slipovers
Its a meeting to improve the next sprint.
Always good to know what we did in last sprint (goood or bad )and improvements)
product backlog,
sprint backlog,
stand up meeting,
sprint planing meeting,
Retrospective meeting.
So We can say we have a complete list of items to do in future for delivery(tasks, bugs etc) That is called product backlog. Now Product owner is the person we prioritize the items which he/she wants to take first. From those items we start the sprint. For that we do sprint planning meeting.
we give story points to each task(story). Story points is kind of estimation for the task which we will take in the sprint. Now we choose the scrum master from the team, who take cares daily standup meeting. I will explain about standup. Scrum master can be any person from the team. We mostly rotate that role after every sprint.
EX:-
Assume we have 20 tasks (stories) to complete in next 2 weeks . That is a sprint and We say sprint starts. Sprint can be 2,3 weeks, but i prefer 2 weeks. there is no hard rule for that.
Now sprint has been started. Every Team membeer picks a story from the sprint ( That can be combined for 2-3 team members for a single story) and start working on that. Next day(every day) we do standup meeting. Now in standup meeting (mainly scrum master arranges that) whole scrum team will standup
together will tell only 3 things - what he/she did yesterday, what he will do today and is ther any impediments.
So the point here comes is how we see progress of stories everyday (What i did is created a board and put every story on that sticky of every story and every day we can move them on board from start-finish).
suppose, client requirement changed in between thn wht will be next step in scrum ??
yes, If you are working on some story and immediately u came to know things has been changed. That can affect only one story or whole sprint. If only one story get affected u can skip tat and start new one. Now product owner will make a task for the new stuff which came and team will pick that in next sprint as per priority.
sometimes we closes the sprint if whole flow changed and start the process again. here product owner plays a big role
the main things is once sprint start we can't add/remove any story from that..
ok documentation always helpful, but That should be minimal. What I do ask developers to write some comments on there code and documents the flow. If you have to test some feature we shold create a test strategy for that.
Agile don't oppose documentation, only support minimal and meaningful one
what is retrospective document ?
When the sprint ends we do a demo to product owner. And We do a retrospective meeting.
In that we mainly document (+ve, -ves of print) you can say what we have learnt from the sprint, what we can improve)
Like in starting days people dont understand the estimation properly the story points system.
We decide what are slipovers
Its a meeting to improve the next sprint.
Always good to know what we did in last sprint (goood or bad )and improvements)
Comments
Post a Comment