Scrum.org

JANUARY 25, 2021

TL; DR: Scrum Master Job — 4 Steps to Identify Suitable Employers or Clients. Are you considering a new Scrum Master job? Don’t worry; there are four steps of proactive research to identify suitable employers or clients for Scrum Masters and avoid disappointment later. Shall I notify you about articles like this one?

SCRUM 195

SCRUM Technical Review Engineering Lean 195

Project Pulse Journal

APRIL 15, 2024

This Article allows you to explore these methodologies in-depth, tailor them to fit your unique project needs, and wield them to achieve unparalleled project outcomes. Ready to transform your approach to project management and software development? It encourages continuous delivery and improvement without the fixed iterations of Scrum.

Software Review 52

Software Review Technical Review Agile SCRUM 52

Scrum.org

AUGUST 18, 2023

Whether teams are new to Scrum or refining their methods, this remains a challenge. The answer lies in the transformative potential of Value Stream Mapping within Scrum. Instead, Scrum makes these challenges transparent, allowing teams to recognize and address them. Welcome to the first post.

SCRUM 162

SCRUM Software Review Technical Review Software Engineering 162

Scrum.org

JUNE 13, 2022

TL; DR: Scrum Developer Anti-Patterns. After covering the anti-patterns of the Scrum Master, the Product Owner, and the stakeholders, this article addresses Scrum Developer anti-patterns, covering all Scrum Events and the Product Backlog artifact. Shall I notify you about articles like this one?

Underperforming Technical Team 151

Underperforming Technical Team SCRUM Technical Review Software Review 151

Herding Cats

MAY 10, 2019

Taxonomy-Based Risk Identification,” Marvin Carr, Suresh Konda, Ira Monarch, Carlo Ulrich, and Clay Walker, Technical Report, CMU/SEI-93-TR-6, Software Engineering Institute, June 1993. IEEE Transactions on Software Engineering , Vol. Software Engineering Institute, January 1996. De Meyer, C. Loch, and M.

Risk Management 38

Risk Management Risk Technical Review 2002 38

MPUG

MAY 14, 2021

I got junior software engineers, software engineers, senior software engineers. I know I’m going to have a senior software engineer and I want him working on these tasks [inaudible 00:12:15] who that is. ” So, in this case, I see the junior software engineer is costing me $1.50

Performance Measurement 59

Performance Measurement Underperforming Technical Team Software Engineering Engineering 59

Herding Cats

MAY 11, 2019

Taxonomy-Based Risk Identification,” Marvin Carr, Suresh Konda, Ira Monarch, Carlo Ulrich, and Clay Walker, Technical Report, CMU/SEI-93-TR-6, Software Engineering Institute, June 1993. IEEE Transactions on Software Engineering , Vol. Software Engineering Institute, January 1996. De Meyer, C. Loch, and M.

Risk Management 35

Risk Management Risk Technical Review 2002 35