Scrum.org

SEPTEMBER 23, 2019

The first article of this series will address the Scrum Master engagement with the Development Team. Scrum Master Engagement with the Development Team. Following this layout, there are three main scenarios for the Scrum Master’s support of the team: The Co-located, Stable Scrum Team Scenario.

Development Team Review 134

Development Team Review SCRUM Software Review Technical Review 134

Scrum.org

APRIL 7, 2022

Team cognition is similar in the sense that the entire team can be thought of as a body, where each member (the limbs) has to learn how to coordinate their work effectively to move forward. This shared understanding is captured in the “team mental models” that drive team cognition. It takes time to develop teams.

Underperforming Technical Team 155

Underperforming Technical Team 2007 2006 2009 155

Leading Answers

JUNE 22, 2022

Willingness to take personal risks. This includes what success looks like and the benefits it will bring to the sponsoring organization, the users of the end result, and the team members who created it.   Ability to empower - We should make use of people’s knowledge and skills by trusting them to do a good job.

Leadership 193

Leadership Underperforming Technical Team Development Team Review Energy 193

Project Pulse Journal

APRIL 15, 2024

Limit Work in Progress (WIP) – By limiting WIP, Kanban encourages teams to complete current tasks before taking on new ones, thus reducing multitasking and focusing on quality and efficiency. Feedback Loops – Incorporate regular meetings to review and adapt your workflow based on feedback.

Software Review 52

Software Review Technical Review Agile SCRUM 52

nTask

MARCH 10, 2021

In 2002, Bill Wake published in his article the inconsistencies that arise from certain terms that are used within teams, including that if “done.”. It took until 2007 for the Definition of Done (DoD) to be a widespread full-fledged practice. Managed by the development team. ”.

Software Review 78

Software Review Technical Review 2002 2007 78

Herding Cats

APRIL 16, 2019

Business, Technical, Systems, Risk, and Project Management Briefings and Presentations. Risk Management (#RM). The following material comes from conferences, workshop, materials developed for clients. Business, Technical, Systems, Risk, and Project Management. Table of Contents (Click the Name to go to Section).

Technical Review 42

Technical Review Performance Measurement Underperforming Technical Team Governance 42

MPUG

OCTOBER 24, 2019

You may wish to use this transcript for the purposes of self-paced learning, searching for specific information, and/or performing a quick review of webinar content. We’re going to take a quick review of Agile options and approaches. What are my risks? You may watch the live recording of this webinar at your convenience.

Agile 40

Agile Technical Review Software Review Underperforming Technical Team 40