Agile Principle
Agile Principle helps to deliver small set of functionality with each iterations. Each iteration helps in evolving more productive rules for next iteration by reviewing within business owner and development team.
Advantage
Scrum
Scrum process is an implementation of agile principles to develop software with efficient teamwork in iterations (called Sprint).
Sprint - is usually of 2-3 weeks cycle to produce deliverable.
Roles
Product Owner - is representative of business. Product owner creates user stories, prioritize them and add it in Product Backlog. Most important responsibility is make sure development team deliver real value to business with each sprint.
Scrum Master - provides interface between Product owner and development team. Main responsibility is to provide support/help to both of them. Helping product owner in writing user stories and helping development team in overcoming any impediments they are facing.
Senior in team can play this part-time role.
Development Team - is appropriate mix of 4-9 team members comprising senior/junior developers & testers team. Ideally team is self manageable would not require managers for daily team operations.
Work Flow:
Sprint Planning meeting : All 3 roles members join this meeting to create product backlog items. Product owner would communicate most valuable deliverable business is expecting. Scrum master would input the team availability for the sprint. And team would divide requirements into tasks and estimate efforts required. Scrum master would then commit for deliverable according to team availability.
Daily Stand ups Meeting : Motive is daily update on progress of tasks team is working on. Every team members mentions 3 things -
1. What they worked on yesterday
2. What they will be working on today
3. Any impediments they are facing.
Its time-boxed for 15 mins so all detailed discussion should be avoided and separate meeting can be arrange for it.
Sprint Retrospective meeting : at the end of sprint, team discuss what were good, bad & to improve points in the sprint. These points are discussed and noted by Scrum master and act as guidelines for coming sprints.
Task Grooming session : Before starting work on tasks they are estimated for the efforts(time) required. Next tasks from product backlog are picked and assigned to team for understanding and investigation. In grooming session, all picked tasks are discussed. The developer investigated the task should provide some more details about the task for other to estimate.
Scrum master records every individual estimate suggestion and discuss for any anonymity. Once all agrees, the task efforts are assigned.
In my personal opinion scrum model is very effective in increasing team performance. Also it keeps developer very closely related to overall project progress.
Agile Principle helps to deliver small set of functionality with each iterations. Each iteration helps in evolving more productive rules for next iteration by reviewing within business owner and development team.
Advantage
- Quick response time to urgent issues.
- Delivery oriented
Scrum
Scrum process is an implementation of agile principles to develop software with efficient teamwork in iterations (called Sprint).
Sprint - is usually of 2-3 weeks cycle to produce deliverable.
Roles
Product Owner - is representative of business. Product owner creates user stories, prioritize them and add it in Product Backlog. Most important responsibility is make sure development team deliver real value to business with each sprint.
Scrum Master - provides interface between Product owner and development team. Main responsibility is to provide support/help to both of them. Helping product owner in writing user stories and helping development team in overcoming any impediments they are facing.
Senior in team can play this part-time role.
Development Team - is appropriate mix of 4-9 team members comprising senior/junior developers & testers team. Ideally team is self manageable would not require managers for daily team operations.
Work Flow:
Sprint Planning meeting : All 3 roles members join this meeting to create product backlog items. Product owner would communicate most valuable deliverable business is expecting. Scrum master would input the team availability for the sprint. And team would divide requirements into tasks and estimate efforts required. Scrum master would then commit for deliverable according to team availability.
Daily Stand ups Meeting : Motive is daily update on progress of tasks team is working on. Every team members mentions 3 things -
1. What they worked on yesterday
2. What they will be working on today
3. Any impediments they are facing.
Its time-boxed for 15 mins so all detailed discussion should be avoided and separate meeting can be arrange for it.
Sprint Retrospective meeting : at the end of sprint, team discuss what were good, bad & to improve points in the sprint. These points are discussed and noted by Scrum master and act as guidelines for coming sprints.
Task Grooming session : Before starting work on tasks they are estimated for the efforts(time) required. Next tasks from product backlog are picked and assigned to team for understanding and investigation. In grooming session, all picked tasks are discussed. The developer investigated the task should provide some more details about the task for other to estimate.
Scrum master records every individual estimate suggestion and discuss for any anonymity. Once all agrees, the task efforts are assigned.
In my personal opinion scrum model is very effective in increasing team performance. Also it keeps developer very closely related to overall project progress.
