Scrum Archives - Laman 3 dari 7

Januari 26, 2022 vpadmin

Your Agile Team: Too Big or Too Small?

Most Agile and Scrum training courses refer to a 7 +/- 2 rule, that is, agile or Scrum teams should be 5 to 9 members. Scrum enthusiasts may recall that the Scrum guide says Scrum teams should not be less than 3 or more than 9. Where does this thumb rule come from? and Why?

Januari 26, 2022 vpadmin

Do More with LeSS (Large Scale Scrum) Framework: with Tool Illustration

LeSS was created by Bas Vodde and Craig Larman from practical experience in scaling up Scrum, founded as the LeSS Company in 2014. The “More with LeSS” principle is at the heart of LeSS (Large Scale Scrum). Complex product development doesn’t require complex solutions. It requires a deep understanding of the essence of the problems, which can then be solved with simpler solutions.

Januari 26, 2022 vpadmin

When Should Use Which? User Story / Use Case / Feature / Backlog Item

We always come across these terms in software development. Sometimes people a piece of software feature — requirement/ use case, backlog items …. What is the convention of the software people for using that or which?

Januari 26, 2022 vpadmin

What is an agile estimate? What are the common pitfalls?

In software development , the usual “estimation” includes a quantitative evaluation of the work required to perform a given development task; this is usually expressed in terms of duration (hour / day) or estimated unit (story point). The purpose is to consolidate a number of such individual estimates in order to obtain an indication of the overall duration, work or cost of the software project.

Januari 26, 2022 vpadmin

Sprint Planning: Forecasting vs Committing

In the summer of 2011, Ken Schwaber and Jeff Sutherland revised their Scrum Guide. In it, they removed one long established behavior known to Scrum, which is the commitment the team makes to the product owner and the customers. Commitment was replaced by forecast. They say that teams may forecast their work, but not commit to it.

Januari 26, 2022 vpadmin

What is the difference between user story and acceptance criteria?

Definition of Done (DoD) is a list of requirements that a user story must adhere to for the team to call it complete. While the Acceptance Criteria of a User Story consist of set of Test Scenarios that are to be met to confirm that the software is working as expected.

Januari 26, 2022 vpadmin

Sprint Review vs Sprint Retrospective

Each sprint ends with a two-part sprint review meeting. Such a meeting starts with a customer review and demonstration and ends with the team retrospective. Both of these components occur on the last day of the sprint. The Sprint Review focuses on the “inspect” and “adapt” of the increment (Potentially shippable), while the Sprint Retrospective give more focus on the “inspect” and “adapt” of the process of the sprint.

Januari 26, 2022 vpadmin

Scrum: INVEST in Good Stories by Achieving SMART Tasks

The INVEST as a reminder of the characteristics of a good quality Product Backlog Item (PBI) (or user stories) commonly written in user story format. But what are characteristics of a good user story? The acronym “INVEST” can remind you that good stories should be

Januari 25, 2022 vpadmin

What is the frustration most Scrum Team Experienced?

What has proven to be the strength of Scrum the past 20 years? What should be the focus of Scrum the upcoming 20 years? What of Scrum frustrated you the most so far? What connects you to Scrum? What is a small improvement that could be added to Scrum?

Januari 25, 2022 vpadmin

Do It Yourself Automated Scrum Process

Seamlessly navigate the entire scrum process in a single, beautifully designed scrum process canvas. Perform scrum activities quickly, easily and seamlessly. Keep the whole team fully engaged. Our agile software makes agile projects simple and effective.