Scrum.org

AUGUST 1, 2022

Each post discusses scientific research that is relevant to our work with Scrum and Agile teams. You can observe implicit coordination in Scrum teams when you look at how work moves across a Scrum board, or on- and of the Sprint Backlog. This is also why the Scrum framework includes the Definition of Done.

2004 230

2004 2010 2009 2016 230

ProjectManager.com

AUGUST 28, 2018

Thanks to the evolution of modern business practices, Agile , an iterative approach to planning and guiding the project process, is on the mind of nearly every manager. So, if you want to take advantage of this framework you’ll probably be wondering, “What is a Scrum, what is a Scrum team and what are the roles that makes up that team?”

SCRUM 118

SCRUM Development Team Review 2016 Agile 118

Agilemania

JULY 20, 2022

It’s no secret that SAFe® is the talk of the Agile town these days and there is a huge demand for SAFe® Program Consultants (SPCs) to be catalysts of SAFe® implementation. Since its release in 2016, the number of people getting SAFe® SPC Certified has been increasing each year. Enhancing your skills. Author's Bio.

Consulting 94

Consulting 2016 Certification SCRUM 94

Scrum.org

SEPTEMBER 3, 2019

“We want to be more agile in our delivery.” “We How can we do Scrum well?” How do we even begin to find, develop and retain motivated individuals? The good news is, agility has mechanisms, mindsets and ideals already built in to motivate team members and give them purpose in their everyday work. Taking an Agile approach.

Agile 112

Agile 2016 2017 2018 112

International Institute for Learning

JUNE 22, 2022

Is there a dark side to agility? The approach many Agile “purists” will expound on is that you must do things a certain way, or if that way of working does not work, you have failed, and it’s your fault. The opposite of agile, thus agilists impose anti-agility practices termed, “agile fragility.”

Agile 59

Agile Lean PMI Innovation 59

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!”. Step one - The interview. .

2017 173

2017 2018 2016 SCRUM 173

Digite

MAY 15, 2018

This article is the fourth in a series of “Kanban and Scrum – Stronger Together”. In the most recent post in Steve Porter’s series, Yuval Yuret presents Scrum in a manner that is intended to educate Kanban teams. Values shouldn’t be expressed as goals like they are in the Scrum Guide. Disclaimer.

Development Team Review 93

Development Team Review Software Review Underperforming Technical Team SCRUM 93

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 77

SCRUM 2013 2016 2017 77

Herding Cats

NOVEMBER 12, 2016

The paper Agile Base Patterns in the Agile Canon , Daniel R Greening, 2016 49th Hawaii International Conference on System Sciences is an important contribution to the discussion of agile at scale in organizations beyond 5 developers at the table with their customer. The Agile Cannon is composed of 5 elements.

Agile 61

Agile 2009 2008 2011 61

Herding Cats

NOVEMBER 7, 2016

And the same process is applied to the Scrum development processes on those projects. . Believing is Seeing: Confirmation Bias Studies in Software Engineering, “Magne Jørgensen and Efi Papatheocharous, 41st Euromicro Conference on Software Engineering and Advanced Applications (SEAA). Tanilkan, Hans Gallis, Anette C.

Estimate 64

Estimate 2006 2005 2013 64

International Institute for Learning

JUNE 22, 2022

We simply need to start judiciously applying the principles of lean-agile management. The foundational practices of Lean, Kanban, Scrum, and SAFe (Scale Agile Framework) were designed to create the space for us to focus on “real work.”. Both traditional and agile project management measures progress by creating items of value.

Technical Review 52

Technical Review Software Review Lean PMI 52

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. & Zein, S.,

Estimate 40

Estimate Software Review Software 2012 40

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. Project risk management: lessons learned from software development environment,” Young Hoon Kwak and Jim Stoddard,” Technovation , 24(11), pp.

Risk Management 38

Risk Management Risk Technical Review 2002 38

Stepping Into Project Management

AUGUST 6, 2018

The book has been recently published in Amazon and if you have heard of Agile, work as part of Agile teams or would like to have a better understanding how to make it across countries to work as one team- the challenges and the tools that will help you bribe the gap, this book is for you. That’s how we decided to write a book.

Agile 40

Agile Leadership 2016 Influencer 40

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. 2128, International Technical Paper , 2016.

Risk Management 35

Risk Management Risk Technical Review 2002 35

MPUG

OCTOBER 9, 2019

Please find below a transcription of the audio portion of Tim Runcie’s Agile Series Part 1 webinar being provided by MPUG for the convenience of our members. Kyle: Hello everyone and welcome to today’s MPUG training series, part one, Understanding and Incorporating Agile Project Management. It’s not all or nothing.

Agile 40

Agile Technical Review Lean Underperforming Technical Team 40

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. Jeff Bezos, founder of Amazon, likes to use the “two-pizza rule” for strategy and development teams. Martine Haas and Mark Mortensen, “The Secrets of Great Teamwork”, Harvard Business Review, June 2016.

Underperforming Technical Team 52

Underperforming Technical Team 2022 Technical Review 2002 52

Digite

MARCH 8, 2018

In this 2-part series, we are honored to publish a couple of blog posts by (2016 Brickell Key award winner) Christophe Achouiantz, Kanban thought-leader, consultant and coach. This article was originally published on Lean-Agile Software Development blog and can be found here– [link]. Now, Good luck!

Lean 79

Lean Underperforming Technical Team 2016 Initiating 79

Herding Cats

MARCH 11, 2017

This is the motivation for short work intervals found in agile development. . Using the Agile Methodology to Mitigate the Risks of Highly Adaptive Projects,” Dana Roberson and Mary Anne Herndon, 10 th Annual CMMI Technology Conference And User Group , November 5 – 8, 2012, Denver, CO. The probability of something happening.

2003 46

2003 2014 2015 2011 46

LiquidPlanner

NOVEMBER 2, 2017

He explains how to succeed or fail fast for projects that are too uncertain to use waterfall project management and too complex to succeed with agile project management. While Abeid hasn’t released a new podcast since 2016, the archives are still worth exploring. Cost: Coursera: Agile Development Specialization.

Technical Review 113

Technical Review 2018 Certification Underperforming Technical Team 113

Herding Cats

APRIL 4, 2019

Verlag, 2016. Project Risk Quantification: A Practitioner’s Guide to Realistic Cost and Schedule Risk Management , John Hollmann, Probabilistic Publishing 2016. The Economic Foundations of Risk Management: Theory, Practice, and Applications 1st Edition , Robert Jarrod, World Scientific, 2016. Alexandre Vidal, Springer?Verlag,

Risk Management 43

Risk Management Risk 2003 2011 43

Herding Cats

APRIL 16, 2019

Agile Project Management (#APM). Agile Software Development (#ASD). Integrating Agile and Earned Value Management (#AEVM). Agile and Earned Value Management Bibliography of papers, books, and thesis (#Biblio). Those lessons are directly transferable to the management of software development teams.

Technical Review 42

Technical Review Performance Measurement Underperforming Technical Team Governance 42

Planio

JULY 22, 2020

Scrum: The Art of Doing Twice the Work in Half the Time. If you’re also interested in Agile project management, pair the PMBOK with the PMI’s new Agile Practice Guide or our own Guide on How to Pick the Software Development Process that’s Right For you. Scrum: The Art of Doing Twice the Work in Half the Time.

2020 148

2020 Underperforming Technical Team Technical Review Software Review 148

MPUG

MAY 6, 2021

Throughout this, I will try and touch on traditional, agile and hybrid as a way of saying they’re all the same, but they’re all very different. It is taking both traditional waterfall and agile and pushing them together into a project or a program. And then team cohesiveness especially in agile environment.

Performance Measurement 52

Performance Measurement Underperforming Technical Team Software Review Governance 52

Paymo App

JANUARY 19, 2018

Project management methodologies – Agile, Waterfall, PRINCE2, PRiSM, Six Sigma, Critical Path, and many more. Tools for project managers – collaboration tools, video chat systems, project management software, and all the apps that you need to start a project. Scrum certifications. Professional Scrum Product Owner.

2018 111

2018 Prince2 Certification Technical Review 111

Leading Agile

OCTOBER 1, 2018

Mike Cohn’s August 2016 article, The Dangers of a Definition of Ready describes certain problems that can occur when a team uses the concept of a Definition of Ready. The use of one or another agile-style technique doesn’t “lead to” or “cause” that. There’s no Magic “Agile” Switch.

Software Review 104

Software Review Underperforming Technical Team Technical Review Infrastructure 104