Scrum Team Activities Finding techniques for effective product

Scrum - Team Activities • Finding techniques for effective product backlog management Product Owner • Helping the scrum team understanding the need for clear & concise product backlog items • Facilitates scrum implementation • Coaching in self-organization & teamwork & removing impediments from the development team Scrum Master Development Team • Helps the development team to create high-value products • Facilitates scrum implementation • Leading & coaching the organization in its scrum adaption, planning scrum implementation within the Organization organization • Helping employees & stakeholders understand & enact scrum & empirical product development

Scrum - The 5 Dysfunctions Inattention To Results Always focusing on individual 01 performance than whole team, Getting easily distracted & losing achievement oriented employees Avoidance of Acc. Encouraging mediocre performance from the team 02 member & lack motivation to complete the tasks on time Lack of Commitments Creating ambiguity about direction 03 & spending a lot of time on analysis, team must commit to decision despite initial disagreements Fear of Conflict Once trust is established, team is unafraid of debate about 04 ideas, hesitating to engage in Absence of Trust healthy conflicts Hiding weakness from each other and hesitating to 05 request for help, teamwork is founded in vulnerability.

Scrum Process (3 D Model) Pre-Game Staging Sprint VISION Development Sprints Wrapper Sprints 24 Std. PRODUCT BACKLOG SPRINT 4 WEEKS INCREMENT SPRINT REVIEW SPRINT PLANNING x 3 -4 PRODUCT

Scrum Process Model Sprint Backlog § Features selected for Sprint § Approximated by team § Team responsibility 24 h SPRINT TIME-BOX Product Backlog Working Code Ready For Distribution Backlog Tasks Sprint Planning Meeting Daily Scrum Meetings Sprint Review meetings • Reassess product backlog • Finishes since last meeting • Trial features • Evaluate sprint backlog • Today’s schedule • Retrospective on sprint alterations • Carry out • Accelerator/roadblocks

Scrum Process Model PREPARATIONS RELEASE Sprint Planning Meeting Daily Scrum or Daily Work Update § Business Case & Funding Product § Contractual Agreement & Vision Backlog § Initial Product Backlog § Initial Release Plan § Stakeholder Buy-in, Assemble Team • Product Owner SCRUM PROCESS • Scrum Master Product Increment • Team Members • Stakeholders • Users Sprint Retrospective Sprint Review

Scrum Process Overview PLANNING & HIGH DEVELOPMENT PROCESS LEVEL DESIGN PHASE OVERVIEW The pre game phase concerns about Develop two things : planning and architecture. This phase of scrum process is very broad if the product is new but if it is an existing system that need to be enhanced. Pre-Game (Phase 1) The management ends development Warp process &the product is being prepared for a release. This includes : integration, Adjust testing, user documentation, training and Review Mid-Game (Phase 2) marketing material preparation. Post-Game (Phase 3)

Scrum Board Overview STORIES 01 TO DO’S Description Text ONGOING DONE Description Text Write something about your story Description Text or its titles. 02 Description Text Write something about your story or its titles. Description Text

Scrum Board Overview TO DO’S ONGOING Description DONE Burndown Chart Description Text SPRINT GOAL : Beta Ready Release Text Description Text 2000 1500 Projected Finish 1000 Description Text 500 Description Description Text Text Description Text 0 1 5 10 15 Unplanned Items Next Step Description Text

Scrum Product Backlog OWNER ESTIMATE REMAMING Task Description 1 TB 1 day 2 Task Description 2 TB 4 days 1 3 Task Description 3 TB 16 days 1 4 Task Description 4 FU 10 days 1 5 Task Description 5 FH 4 days 2 6 Task Description 6 CK 6 days 2 7 Task Description 7 YO 8 days 3 8 Task Description 8 TB 2 days - 4 9 Task Description 9 BB 1 days - 5 10 Task Description 10 TB 1 days - SPRINT ID 1 1 1 BACKLOG ITEM

Scrum Product Backlog Working Hours Id Backlog Item Assigned To Due Status Estimate Actual 1 Task Description 1 None Day 10 Open 8 2 2 Task Description 2 TB Day 8 Open 4 3 3 Task Description 3 NB Day 12 Open 4 0 4 Task Description 4 - - Open 2 0 5 Task Description 5 ST - Open 2 0 6 Task Description 6 - - Open 4 0 7 Task Description 7 - - Closed 2 0 8 Task Description 8 - - Closed 9 Task Description 9 - - Closed 27 5 TOTAL

Scrum Product Backlog 02 HIGH | Write about your product back log here. Project Description : 07 Project Task ID 05 HIGH | Write about your product back log here. Assigned To Priority Status 02 MEDIUM | Write about your product back log here. Story Pt : 05 001 John Doe High Feedback : Write feedback related to your project task that what challenges you faced, how was team execution, issue generated during implementation, also provide proper 06 LOW | Write about your product back log here. description or summary regarding it. Progress Bar/Completion (%) : 08 LOW | Write about your product back log here.

Scrum Sprint Backlog Monday 01. Code the first phase of application i. e. login 04 08 02. Design the setting screen flow of user profile 03. Meet the client for further discussion on project Tuesday 12 Wednesday Thursday 04 08 16 08 04 08 16 16 12 04. Automate the testing of first developed phase 05. Assign task to junior developer 12 08 12 06. Consult senior UX designer for application flow 07. Check maintenance period of server Friday 12 08 Saturday 12 04 04 16 04 12

Scrum Sprint Backlog DEPARTMENT Human Resource TASK DESCRIPTION OWNER HOURS REG. M T W Task Title 01 T F Write description here TB 12 4 8 4 Task Title 02 Write description here TB 40 12 10 16 4 Task Title 03 Write description here KV 50 8 16 12 16 8 Task Title 04 Write description here FH 30 12 12 8 Task Title 05 Write description here FG 2 8 8 8 4 8 Task Title 01 Write description here TB 8 16 4 Task Title 02 Write description here NS 4 8 16 Task Title 01 Write description here GE Financial Dept. Marketing Dept. 4

Ideal Scrum Sprint Backlog Ideal, sprints is a fixed time period of 1 -4 weeks; its depends upon the team to schedule the sprint. Scrum team identify the problems faster, but sometimes its seems uncomfortable. TIME 2000 1800 Burndown Chart It’s a graphical representation of work remaining to be versus time. Burndown charts are a run chart of outstanding work. It is useful for predicting when all of the work will be completed. Bu rnd 1600 WORK REMAINING # POINTS Ideal Sprint & Burndown Chart 1400 1200 ow n. V elo city 1000 800 600 Projected Finish 400 200 0 1 5 10 15

Scrum Burndown Chart 250 Remaining Tasks 225 200 Remaining Effort Remaining & Completed Task Remaining Efforts (in hrs) 175 150 125 100 75 Completed Tasks 50 25 0 Day 1 Day 2 Day 3 Day 4 Day 5 Day 6 Day 7 Day 8 Day 9 Day 10 Day 11 Day 12 Day 13 Day 14 Day 15 Day 16 Day 17 Day 18 Day 19 Day 20 Day 21 Day 22 Day 23