Get started with Jira by Coursea

-
Get started with Jira by Coursea

Comments

Post a Comment

Popular posts from this blog

What is the ‘Navigating the Scrum Events’ Series?

-
Image
Source: https://www.scrum.org/resources/blog/navigating-scrum-events-sprint-review What is the ‘Navigating the Scrum Events’ Series? If you or your team are new to Scrum, you can use this as a starting point to answer, “what should we be doing and why?” for each Scrum Event. If your team is more experienced but you feel like you’re drifting away from healthy behaviors and patterns and you’re not sure how to course correct - you can use this series as a baseline to reset and start re-aligning your team. This is NOT the end-all-be-all perfect way to operate for all scenarios - but a straight-to-the-point tactical list of steps to help you get to the basic outcomes you need at the end of the event. The Sprint Sprint Planning Daily Scrum Sprint Review Sprint Retrospective Sprint Review - What’s The Point? The purpose of the Sprint Review straight from   the Scrum Guide  is “to inspect the outcome of the Sprint and determine future adaptations”. The key to this instance of “in...
Read more

Product Owner - Role And Responsibilities and Po V/s SM

-
Image
What is a Product Owner?  Reference : https://www.c-sharpcorner.com/article/product-owner-role-and-responsibilities/ To be precise, a product owner is a scrum development role for a person who represents the business or user community, and is responsible for working with the user group to determine what features will be included in the product release.   Image Source – ProductCoalition.com   What are a Product Owner’s Responsibilities? The Product Owner (PO) represents the business to the development team and the Scrum team to the business folks. The PO  is one person, not a committee or group of people. The PO has product vision. The PO  owns the budget and is responsible for the success of the product. He/she is part of the Scrum team – closely works with the development team and Scrum Master throughout the sprint. The PO owns the product backlog and directs product development through product backlog prioritization. Strives to maximize the...
Read more

To calculate how many user stories can be assigned in a 2-week sprint

-
 To calculate how many user stories can be assigned in a 2-week sprint with 3 developers and 1 QA, where each developer works 6 hours per day, we need to consider the total available hours and how many story points the team can realistically complete. Example Calculation Assumptions: Sprint Duration: 2 weeks (10 working days). Work Hours per Day per Developer: 6 hours. Total Developer Hours: 3 developers × 6 hours/day × 10 days = 180 hours. Work Hours per Day for QA: 6 hours. Total QA Hours: 6 hours/day × 10 days = 60 hours. Average Velocity: Assume the team typically completes 25 story points per sprint. Estimating User Stories Allocate Story Points to Developers: Let’s assume each story is 5 story points. If each story requires approximately 30 developer hours (5 story points/story), the developers could handle 6 stories: 180  developer hours 30  hours per story = 6  stories \frac{180 \text{ developer hours}}{30 \text{ hours per story}} = 6 \te...
Read more