#scrum guide

[tntra]

The Impact of Scrum: Enhancing Work Quality, Productivity, and Work-Life Balance - Tntra

Maximize work quality, productivity, and work-life balance by adapting Scrum to your organization. Learn the key considerations for successf

Discover the profound impact of Scrum on work quality, productivity, and work-life balance in this insightful blog by Tntra. Explore how implementing Scrum methodologies can enhance collaboration, efficiency, and overall team performance. Learn about the benefits of iterative development, continuous improvement, and effective project management techniques. Dive into real-world examples and practical tips to harness the transformative power of Scrum in your organization. Embrace a new way of working and unlock the potential for success.

[rachaelwilterdink]

The once Self-organized, now Self-managed Scrum Team

Check out my blog: The once self-organized, now self-managing agile Scrum Team

Let me begin this blog with the fact that the updated 2020 Scrum Guide changed the term “self-organizing” to “self-managed”. I think this was a very appropriate change because that is what Scrum Teams truly do. They don’t just decide how to work together, they also direct their own work without anyone else telling them what to do. This freedom provides autonomy and lets them create the best plan…

View On WordPress

[solution-delivery-blog]

Illustration to the Scrum Guide

The Daily Scrum is not a reporting session but an internal discussion of the Development Team.

[solution-delivery-blog]

A pool of more than 100 Scrum test questions

This PSM I exam simulation test works from a pool of questions:

Basic questions target the fundamentals of Scrum.

Intermediate questions target the detailed rules of the Scrum Guide.

Scenario-based advanced questions also reflect on the Scrum Guide, however, the test taker has to understand the context.

Expert questions target agile practices not detailed in the Scrum Guide.

[solution-delivery-blog]

An illustration to the Scrum Guide

Inputs to Sprint Planning:

the Product Backlog: an ordered list of the deliverables as described in the Product Backlog chapter;

the latest product Increment: the work delivered as described in the Increment chapter; Ideally it has been inspected on the Review meeting and the feedback is collected; less ideally it contains leftover work yet to be done;

the projected capacity of the Development Team during the Sprint: in real terms, the number of available workdays of team members with given skills in the coming Sprint; The measurement unit is not necessarily ‘workday’;

and past performance of the Development Team: traditionally measured as velocity (story points delivered per sprint).

Original source: Scrum: The Guide Explained - Sprint Planning

[andreeavisanoiu]

Scrum 101 from the Trenches (1). What no Training Teaches You

Scrum 101 from the Trenches (1). What no Training Teaches You

Scrum is currently the most popular product development framework. It’s also the framework I used the most and I am most comfortable using. It’s a simple framework, but not easy to implement.

I am going to write a Scrum series, where each post will tackle a part of Scrum, with information on its purpose and definition, to which I will add the interesting part: what Scrum training doesn’t teach…

View On WordPress

[zorays]

Master Scrum Certification to Change Command and Control Culture of Organisations

Master Scrum Certification to Change Command and Control Culture of Organisations

We are living in the 4th generation of industry, where most of the organisations have already changed the way of doing work. But there are still a few organisations attempting to change the old management styles and their “command and control” culture. These organizations are not getting positive results from these transition programs because they are just doing single-fix changes in the teams…

View On WordPress

[ullizee]

Scrum and universal truths [update 2018]

Scrum offers simplicity, without being simplistic. No universal truths. (a slightly refined update of a previous blog post)

In 2010, the principal co-creators of Scrum, Jeff Sutherland and Ken Schwaber, agreed on the first version of the Scrum Guide, thereby creating the official BOK (body of knowledge) for Scrum. A few small, functional updates have been released since then. There have been no drastic changes to the core definition of Scrum. The updates are attempts to reduce complexity or have clearer terminology. L…

View On WordPress