1.What is Scrum?
Scrum is a framework that helps the team work together. The Scrum promotes teams to learn through experiences, self-organization when encountering problems, towards victory and continuing to improve with problems encountered.
Speaking of Scrum most of us will be caught in software development, but it fits all teamwork activities. That’s one of the reasons Scrum is so popular. Known as a management framework project_Agile. Scrum describes a set including meeting, tool, and linked roles to structure team structure and management at work.
2.What are sprints?
A Spint is a time-box that helps the team complete a certain block of work with a time.Sprints frame is the heart of Scrum and Agile methodology, if the sprint is implemented correctly to help the team minimize pain. First, it is effective to offer a good quality software product.
“Sprints make management easier, make work faster, with better product quality, and more flexibility with greater response to changes.”
2.1 How to plan and execute scrum sprints
To plan for the next sprint, you need to conduct a sprint meeting . Sprint meeting is an event where the team answers two basic questions: ‘What will it do and how will it work? ‘
Selecting the corresponding jobs in sp is the common work between the Product owner (PO) , Scrum master (SM) and Team dev (TDV) . The PO gives the goal to achieve, then explains the items that produce backlog.
On TDV after creating plan to do ntn to build the item backlog and done before before the sp ends. This work is called a sprint backlog. At the end of Sprint planning as shown in the diagram, the team is ready to start the work of sp on the sprint backlog to change to ” In-progress ” and ” Done “.
During the sp, team check or standup about the work done ntnm. The purpose of this meeting is to help clarify what is likely to affect progress, how to solve the problem if any to achieve the goal of sp.
After 1 sp, the team will demonstrate the work that has been completed at Sprint Review. This is the chance for each mem show to show up with all other mems about the results and with the relevant parties before release production. Limiting in the policy has just been done with the goal to get the next one better, what needs to be improved, this is considered to be a meeting about things that you feel good, not stable, inadequate need to promote What, say your personal opinion in the Sprint Retrospective.
2.2 Do’s and Don’ts
Do:
● Make sure that the team understands and sets up the sprint’s goals and objectives, confirming how to measure how successful sp is. This is the key for all members to go in one direction, towards the same direction with the common goal.
● Make sure you have a nice backlog with priorities (priorities) and a dependency order (dependencies in order). If you do not manage appropriately, it will lead to delays. This is a big problem that needs attention.
● Proceed to the Sprint planning meeting to make sure that the details of the necessary tasks are clear. Benefit members to outline tasks for all stories, bugs, and sprint tasks.
● Finally, after latching on and planning, assign the mems through a certain tool, to make sure all mems are easy after you need to check the information later.
Don’t:
● Do not pull too many stories, tasks that cannot be completed in sprint.
● Don’t forget about the quality of products or teachnical. Need to be sure of both time for QA and non-feature jobs like bugsss and health issues for mems …
● Do not let the members of the team still wonder, freak, not clear about the content in Sprint. Do not be too focused on the speed of task completion, don’t forget the important thing here is that all members are targeted together (same direction). ● Do not try to complete high-risk tasks, or heavy tasks need time to study, in this case do not hesitate to negotiate moving a part to the next Sp.
● In case of unexpected occurrence, the case of such a task is more difficult than the initial estimate, and the performance is affected by other tasks, not to be ignored. An adjustment action is required to deal with that problem.
3.Sprint planning
3.1 What is sprint planning?
Is a Sprint kicks off event. The purpose of Sprint Planning is to define what can be created in the sprint and how to accomplish it. Planning is done by all members of the team.
In Scrum sp is a predetermined time interval to complete all tasks. However, before working, you need to prepare for Sp. You need to specify the time interval to perform sp, goal of sp, and start sp from. If done correctly, it can create an environment in which members are always ready to fight, take the initiative to challenge and succeed. A bad sp planning with non-realistic expectations will leads to the team breaking up.
● The What – After the PO explains the goal of Sp, what is the team’s job in the upcoming sp, and decides to show what corresponds to each different timing in sp.
● The How – TDV will plan what needs to be completed to achieve the sp base goal of the team to communicate with the PO.
● The Who – You cannot go to planning if there is no PO and TDV. PO gives a goal. Team needs to understand, evaluate what can or cannot with that goal. If either PO or TDV does not participate, it cannot be scheduled for sp.
● The Inputs – A good starting point is the base according to what was previously done to list the parts that can be performed at this sp.
● The Outputs – Most importantly, the catches, describe the goal of the game, how to implement it.
Prep for sprint planning meeting Prepare for how good the sprint is? Based on the review of previous, integrated vision with the future to plan for the best considered.
* PRO TIP :. If you spend 2 weeks for 1 sp. Conducting a meeting in the middle of the week is a great way for the team to temporarily break away from the current one and look at the next tasks that will be done in the future. Not only is it helpful for planning preparation, but also through a different view of current affairs. *
Đang đặt một thời gian thời gian cho sprint Planning Should limit the time of planning for each sp to no more than 2 hours per week That is called “timeboxing”. This is the maximum time interval, but before the end of this time period, the members feel ok about the content, they can end this event. Actual Sprint Planning Attendees :: Development team, Scrum master, product owner. When: Start Sprint. Duration: Usually 1 hour per week with sp lasting about 2 weeks, it takes 2 hours of planning meeting. Agile Framework: Scrum. Purpose: Product Owner will give priority to each item. Exchange with development team about each item. And both DevTeam together attempt to est. DevTeam will then propose how well the sprint will complete the item (become The Sprint backlog).
Daily Stand-up Attendees: Development team, Scrum master, product owner. When: Once a day, usually in the morning. Duration: No more than 15 minutes. No need to book rooms, standing will help shorten the meeting time. Agile Framework: Scrum and Kanban. Purpose: Can quickly inform all other members about what’s going on. Not a detailed meeting. The members will answer the following questions: ・ I finished xxxx the day before.・ My intended work today.・ I’m having a problem with xxx.
Iteration review_ Review Repeat Required: Development team, Scrum master, product owner. Optional: People related to Project_ stakeholders. Khi: tại cuối của sprint. Duration: 30-60 minutes. Purpose: Show outputs and receives feedback from stakeholders.
Retrospective Attendees: Development team, scrum master, product owner When: At the end of the sprint Duration: 60 minutes. Agile Framework: Scrum and Kanban. Purpose: Receiving feedbacks for better product quality, better team culture. With repetition through which the team also understands why it encounters that problem, and how to solve it .