Scrum.org

NOVEMBER 15, 2018

Last week marked the official announcement from Scrum.org that I’m finally a Professional Scrum Trainer. Some years ago — in 2012 — I experienced my first Professional Scrum Master class. Some years ago — in 2012 — I experienced my first Professional Scrum Master class. My journey up to this point.

SCRUM 132

SCRUM 2012 2018 Software Review 132

Scrum.org

AUGUST 25, 2022

It is very similar to work engagement (Schaufeli & Salanova, 2014), which we also measure in both the Scrum Team Survey and TeamMetrics (as “team morale”). Self-Determination Theory (Deci & Ryan, 2012) provides a great perspective on what creates intrinsic motivation. In Achieving Quality in Software (pp. References.

Sustainability 183

Sustainability 2015 2014 2013 183

Scrum.org

APRIL 7, 2022

Each post discusses scientific research that is relevant to our work with Scrum and Agile teams. Edmondson (2012) argues that dynamic teaming is important to share and encourage learning. This is also what inspired Edmondson (2012) in her academic work on “teaming”. This post is my attempt to do this. A., & Mesmer-Magnus, J.

Underperforming Technical Team 168

Underperforming Technical Team 2007 2006 2009 168

Scrum.org

FEBRUARY 25, 2020

When I started using Scrum as a software developer back in 2007 I noticed that this new ways of working really worked, then I decided to learn more about and I became a Scrum Master in 2012 and in 2015 I started to teach Scrum, overcoming my fear of public speaking. You love this!”.

2017 174

2017 2018 2016 SCRUM 174

Scrum.org

NOVEMBER 15, 2018

Last week marked the official announcement from Scrum.org that I’m finally a Professional Scrum Trainer. Some years ago — in 2012 — I experienced my first Professional Scrum Master-class. Some years ago — in 2012 — I experienced my first Professional Scrum Master-class. My journey up to this point.

SCRUM 94

SCRUM 2012 2018 Software Review 94

Herding Cats

NOVEMBER 7, 2016

And the same process is applied to the Scrum development processes on those projects. . The primary purpose of software estimation is not to predict a project’s outcome; it is to determine whether a project’s targets are realistic enough to allow the project to be controlled to meet them ‒ Steve McConnell.

Estimate 64

Estimate 2006 2005 2013 64

Agilemania

DECEMBER 13, 2021

The groundwork for SAFe was formed in 4 knowledge areas – agile software development, lean product development, systems thinking, and DevOps. SAFe contains a combination of principles, processes, and best practices that help large organizations in easy adoption of agile frameworks including Lean, Kanban, and Scrum.

Agile 98

Agile Lean Software Review Technical Review 98

Scrum.org

AUGUST 17, 2020

See how approaches like the Scrum Framework and Liberating Structures can prevent some of these biases by bringing in diverse voices and by validating your assumptions against reality. For me personally, it's one of the reasons why I like the Scrum Framework , as it gives guide-rails to help us think and validate our assumptions with data.

2015 221

2015 2014 2004 Influencer 221

Herding Cats

MAY 10, 2019

This blog page is dedicated to the resources used to assess risks, their impacts, and handling strategies for software-intensive systems using traditional and agile development methods. IEEE Transactions on Software Engineering , Vol. Software Engineering Institute, January 1996. México, 1 al 3 de Febrero de 2006.

Risk Management 38

Risk Management Risk Technical Review 2002 38

Herding Cats

MAY 11, 2019

This blog page is dedicated to the resources used to manage the risk encountered on software-intensive systems using traditional and agile development methods. Let's start with a critical understanding of the purpose of managing risk on software development projects. IEEE Transactions on Software Engineering , Vol.

Risk Management 35

Risk Management Risk Technical Review 2002 35

Herding Cats

MARCH 11, 2017

The naturally occurring work effort in the development of a software feature - even if we've built the feature before - is an irreducible uncertainty. Hybrid–Agile Software Development Anti–Patterns, Risks, and Recommendations,” Paul E. Nord, CrossTalk: The Journal of Defense Software Engineering , May/June 2013.

2003 46

2003 2014 2015 2011 46

Herding Cats

APRIL 4, 2019

Research shows that for projects, especially software projects Aleatory uncertainty is the predominant source of risk. So here are some books, handbooks, and guides that sit on my shelf that are used pretty much all the time on the Software Intensive System of Systems we work on. Software Risk Management , Barry W.

Risk Management 43

Risk Management Risk 2003 2011 43

Herding Cats

NOVEMBER 12, 2016

Establish a Zero backlog approach to planning - Scrum creates Sprint Backlog. Highly effective Scrum teams have seven items in Sprint Backlog. Ashkenas, “It’s Time to Rethink Continuous Improvement,” HBR blog [link] (2012). . [3] Jakobsen et al, “Scrum and CMMI – Going from Good to Great: Are you ready-ready to be done-done?”

Agile 61

Agile 2009 2008 2011 61

Herding Cats

APRIL 16, 2019

Here's a collection of presentations, briefings, papers, essays, book content used to increase the Probability of Project Success (PoPS) I've written and applied over my career in the software-intensive system of systems and other domains. Agile Software Development (#ASD). Enterprise IT and Embedded Systems (#EIT).

Technical Review 42

Technical Review Performance Measurement Underperforming Technical Team Governance 42

Herding Cats

JUNE 12, 2018

Yes, this is the basis of any closed loop control system from keeping the room temperature at a specific setting, to the speed control on your car, to managing software development projects in the presence of uncertainty. At a minimum, at the end of every week, a Scrum team assess physical percent complete at the end of the Sprint.

Underperforming Technical Team 40

Underperforming Technical Team Software Engineering Estimate Software Developers 40

Wrike

NOVEMBER 7, 2018

Project Management Software & Tools. Most Popular Agile Tools and Processes: Scrum – 43%. Lean & Test Driven Development (TDD) – 11%. Feature Development Driven – 9%. Dynamic Systems Development Method – 3%. Project Management Software & Tools. 53% use project management software.

2015 60

2015 Technical Review Underperforming Technical Team Software Review 60

Herding Cats

JUNE 12, 2018

Yes, this is the basis of any closed loop control system from keeping the room temperature for a specific setting, to the speed control on your car, to managing software development projects in the presence of uncertainty, using any software method you choose. So the first thing to do is answer the question.

Underperforming Technical Team 28

Underperforming Technical Team Software Engineering Estimate Development Team Review 28

Workzone

AUGUST 4, 2021

This list of alternatives for Asana the project management software will help you identify which project management software you should be using. We’re going to share the top Asana alternative, Workzone, pros and cons of Asana, and 24 other software solutions so you can decide which option is worth researching further.

2021 26

2021 Software Review Technical Review Underperforming Technical Team 26

BeeWits

JULY 3, 2018

Wrike is a project management software that enables you to collaborate with your team efficiently and effectively. As a company, Wrike is the provider of a cloud-based project management and collaboration software, based in Silicon Valley, the San Francisco Bay Area. Let’s get started. What is Wrike? Start a reporting trial now.

Software Review 29

Software Review Underperforming Technical Team Budget Defining 29