ProjectManager.com

MARCH 4, 2022

The scrum methodology was developed as a response to rigid project management approaches such as the waterfall method, which didn’t adapt to the needs of agile product and software development teams. We’ll explore the scrum methodology in-depth, but before that, let’s start with a simple scrum definition. Scrum Values.

SCRUM 366

SCRUM Software Review Development Team Review Underperforming Technical Team 366

International Institute for Learning

JULY 7, 2022

During the last two decades there has been the emergence of a number of software development methods as a response to the inefficiency of existing software development methods in rapidly changing environments (Highsmith, 2004). 2009), include eXtreme Programming (XP) (Beck and Fowler, 2001) and Scrum (Schwaber and Beedle, 2002).

Innovation 59

Innovation Agile 2002 2001 59

Henny Portman

JULY 17, 2020

We get a brief overview of a number of approaches (including agile, BPR, co-creation, kaizen, supply chain cooperation, operational excellence, Scrum, Six Sigma, TQM) and how these approaches relate to the lean philosophy. Eiji Toyoda (1913-2013): build the new car factory based on just-in-time concept (JIT) and a kanban system.

Lean 80

Lean Software Review 2013 Innovation 80

Gunther Verheyen

DECEMBER 19, 2018

In 2013 I accidentally created a book, “Scrum – A Pocket Guide” In 2018 I deliberately evolved my Scrum travel companion into a second edition. I am humbled over the many unanticipated consequences of the accidental creation of my pocket guide to Scrum. In July 2016 they were added to the Scrum Guide.

SCRUM 82

SCRUM 2013 2016 2017 82

MPUG

MAY 10, 2022

For example, Scrum is a methodology which emphasizes delivery in short increments and frequent meetings. Scrum was originally used in software development projects. As a call to action, I recommend you review the 15 th Annual State of Agile Report to be informed about all the benefits and challenges with Agile methods.

Agile 59

Agile 2019 2013 Certification 59

Scrum.org

DECEMBER 23, 2021

Each post discusses scientific research that is relevant to our work with Scrum and Agile teams. Why is code quality so often an issue? Why do software teams?—?despite But also a field that has much to say about code quality and how we can be better developers. Technical Debt and Code Smells.

Software Review 187

Software Review Technical Review Underperforming Technical Team 2015 187

Digite

JUNE 13, 2018

Compared to Scrum, Kanban is a young work-management method. Anderson best articulated its application to software development, in 2013, in the foundational book Kanban: Successful Evolutionary Change for Your Technology Business, and its adoption hasn’t been as universal as Scrum’s during the early days of Agile software development.

Agile 110

Agile Technical Review Cadence Software Review 110

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. A Critical Review Of Risk Management Support Tools,” Irem Dikmen, M. 5, September/October 2011.

Risk Management 38

Risk Management Risk Technical Review 2004 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 2004 35

Project Management Essentials

AUGUST 3, 2019

In 2013, Mike Cohn coined the term scrum smells to describe the signs that a scrum team is in trouble. Scrum masters, agile coaches, and even team members can improve their teams’ performance by spotting these warning signs early and taking corrective actions. Who is the Scrum Master or Product Owner?

Underperforming Technical Team 40

Underperforming Technical Team Agile Technical Review Software Review 40

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. McMahon, Cross Talk: The Journal of Defense Software Engineering , July/August 2015, pp.

2003 46

2003 2014 2011 2015 46

Scrum.org

JUNE 17, 2019

Scrum cumplió 21 años en 2016. Desde 2011 ha habido dos grandes cambios en la guía de Scrum , en 2013 y 2016. Se reforzó el énfasis en el Daily Scrum como elemento de planificación -y no solamente sincronización- y también se cambió el nombre de la reunión de grooming a refinenement. Con muchos cambios.

SCRUM 21

SCRUM 2011 2016 2013 21

LiquidPlanner

NOVEMBER 2, 2017

Hosted by Peter Taylor, this podcast began in 2013 after he published his best-selling book by the same name. We recommend checking out the “Project Management Training Bundle”, which gives you access to the PM certification courses, as well as the Agile and scrum certification courses. Scrum Certifications. Cost: $6,570.

Technical Review 113

Technical Review 2018 Certification Underperforming Technical Team 113

Scrum.org

AUGUST 3, 2020

Dependencies are an epidemic in software development. What the Scrum Guide says: “Cross-functional teams have all competencies needed to accomplish the work without depending on others not part of the team. The team model in Scrum is designed to optimize flexibility, creativity, and productivity.” - K. Schwaber and J.

Underperforming Technical Team 241

Underperforming Technical Team Technical Review Software Review Development Team Review 241

nTask

AUGUST 22, 2019

“Scrum” is a phenomenal subject – i.e. if you are familiar with it. As an Agile project manager, I have seen my fair share of so-called “Scrum Masters” and “Agile Experts” claiming to be masters of their craft. The truth, however, is that they don’t know a lot of things about Scrum and Agile. Introduction – Why Scrum?

SCRUM 132

SCRUM Technical Review Development Team Review Software Review 132

Scrum.org

SEPTEMBER 11, 2020

Everybody wants to Scale Scrum. So you have a couple of Scrum Teams that are working in adjacent areas and you're starting to face some challenges in delivering value in a coordinated integrative way. This is more or less the time you started searching for "scaling agile" "scaling scrum" and exploring your options.

SCRUM 207

SCRUM 2008 2013 Software Review 207

Rebel’s Guide to PM

OCTOBER 28, 2022

A survey showed that teams using Slack had: 32% less email 23% fewer meetings 24% of features (in technical teams) delivered on time 27% less time required for software testing 10% improvement in employee satisfaction. For most projects, you are going to need something else as well to create your Gantt chart or Scrum board, for example.

Technical Review 409

Technical Review Software Review 2013 Software 409

Scrum.org

APRIL 7, 2022

Each post discusses scientific research that is relevant to our work with Scrum and Agile teams. Wang et al (2006) studied software teams tasked with ERP implementations and found that cohesive teams performed significantly better than less-cohesive teams. This post is my attempt to do this. This post is part of our “in-depth” series.

Underperforming Technical Team 175

Underperforming Technical Team 2007 2006 2009 175

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 224

2015 2014 2004 Influencer 224

MPUG

JULY 30, 2020

Please find below a transcription of the audio portion of Rich Murphy’s showcase session, Triskell Software for Enterprise Governance, being provided by MPUG for the convenience of our members. Kyle: Hello everyone, and welcome to today’s MPUG vendor showcase session, Triskell Software for Enterprise Governance.

Government 52

Government Governance Software Review Software 52

MPUG

JULY 30, 2020

Please find below a transcription of the audio portion of Rich Murphy’s showcase session, Triskell Software for Enterprise Governance, being provided by MPUG for the convenience of our members. Kyle: Hello everyone, and welcome to today’s MPUG vendor showcase session, Triskell Software for Enterprise Governance.

Government 52

Government Governance Software Review Software 52

Rebel’s Guide to PM

JUNE 24, 2019

A 2017 survey showed that teams using Slack had: 32% less email 23% fewer meetings 24% of features (in technical teams) delivered on time 27% less time required for software testing 10% improvement in employee satisfaction. For most projects, you are going to need something else as well to create your Gantt chart or Scrum board, for example.

Software Review 225

Software Review Technical Review 2013 2017 225

Wrike

NOVEMBER 7, 2018

Project Management Software & Tools. Most Popular Agile Tools and Processes: Scrum – 43%. Lean & Test Driven Development (TDD) – 11%. Project Management Software & Tools. 77% of companies use project management software, and 87% of high-performing companies use project management software. [5].

2015 60

2015 Technical Review Underperforming Technical Team Software Review 60

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

Herding Cats

MAY 7, 2019

This blog page is dedicated to the resources used to estimate software-intensive systems using traditional and agile development methods. Cost Modeling Agile Software Development,” Maarit Laanti and Petri Kettunen, International Transactions on Systems and Applications, Volume 1 Number 2, pp. Performance Evaluation of non?Markovian

Estimate 40

Estimate Software Review Software 2012 40

MPUG

OCTOBER 9, 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. Today’s session is eligible for one PMI PDU in the technical category and the code for claiming today’s session is on the screen now.

Agile 40

Agile Technical Review Lean Underperforming Technical Team 40

Redbooth

FEBRUARY 20, 2018

In 2013, Moz learned the hard way what can happen when a project gets derailed. It turns out the project was understaffed, the due dates were wildly optimistic, and engineers were forced to follow a “big bang” release style directed towards a single launch with no measures to check progress along the way.

Underperforming Technical Team 74

Underperforming Technical Team Software Review 2013 Agile 74

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 Governance Government 42

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

International Institute for Learning

SEPTEMBER 20, 2022

For instance in the Agile Scrum Methodology [4] it is recommended to have 10 or fewer people in a team. The risk with larger teams is that they can be more vulnerable to poor communication, fragmentation, and free riding due to a lack of accountability [3]. This alone is a good reason to pay attention to the two-pizza rule [5].

Underperforming Technical Team 52

Underperforming Technical Team 2022 Technical Review 2002 52

Herding Cats

SEPTEMBER 19, 2018

Flight software is always an issue where we work, so those ranges are wider even more. Getting the software qualified is about the same variability as getting it certified, so the same range is used. This is a Closed Loop Control Systems for managing the performance of a Software Intensive System of Systems, all developed using Scrum.

2010 43

2010 Technical Review Estimate Software Review 43