MPUG

MAY 10, 2022

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. Organizations may also choose to adopt various methodologies to begin managing in an Agile way.

Agile 59

Agile 2019 2013 Software Review 59

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. Scrum is part of agile software development and teams practicing agile. What Is the Scrum Methodology? Learn More!

SCRUM 335

SCRUM Software Review Development Team Review Underperforming Technical Team 335

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. 3, March 2002. “The

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

OCTOBER 24, 2018

But before going further, let's establish the definitions we need to understand and apply Root Cause Analysis needed to discover the corrective and preventive actions to increase the probability of project success - especially Software Project Success. What factors lead to software project failure?” All for the want of a nail.

2014 45

2014 Aerospace 2011 2013 45

Teamweek

JUNE 17, 2020

” LinkedIn founder Reid Hoffman talked about his agile, project-based hiring approach in a 2013 Harvard Business Review article , explaining that he hires employees on a four-year “tour of duty,” with a check in after two years. The terminology is borrowed from software developers.

Technical Review 90

Technical Review 2013 Consulting Innovation 90

Gunther Verheyen

FEBRUARY 26, 2024

From 2013-2016 I maintained the official “Professional Scrum” series of Scrum.org meanwhile training candidate-PSTs and shepherding the global community of Professional Scrum Trainers and coaches. In 2011 I obtained my license as a Professional Scrum Trainer for Scrum.org from Ken Schwaber (co-creator of Scrum).

SCRUM 74

SCRUM Certification 2016 2011 74

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

Digite

JUNE 13, 2018

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. Creating Your First Kanban Board.

Agile 110

Agile Technical Review Cadence Software Review 110

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. More and different people look for guidance and insights on their journey of Scrum, increasingly in domains beyond software development.

SCRUM 77

SCRUM 2013 2016 2017 77

Herding Cats

JULY 24, 2017

Shipping on time, to specifications, and within budget might be meaningless if a competitor is shipping software that has a greater value to the market. It's suggested from observations, the Cone of Uncertainty (CoU) is not a valid model of how uncertainty behaves in software development projects. Laird and M.

2007 42

2007 2012 2006 2008 42

LiquidPlanner

NOVEMBER 2, 2017

Hosted by Peter Taylor, this podcast began in 2013 after he published his best-selling book by the same name. Cost: Coursera: Agile Development Specialization. This course provides a beginner overview of the Agile methodology, specifically within software projects. Harvard Business Review. The Lazy Project Manager.

Technical Review 113

Technical Review 2018 Underperforming Technical Team Certification 113

Project Management Hacks

AUGUST 4, 2016

In 2013 , the company delivered 1.5 Through many discussions with my husband – who works in software development – I discovered an interest in the technology field. I led an effort to develop a risk-based software development process. What was the most valuable professional development activity (e.g.

2013 28

2013 2003 Technical Review 2010 28

Herding Cats

JANUARY 22, 2017

Barry Boehm's work in “Software Engineering Economics”. This is due to many reasons. We have a target weight at Test Readiness Review of 23KG. 2] System Analysis, Design, and Development Concepts, Principles, and Practices, Charles Wasson, John Wiley & Sons. [3] Software Engineering Economics”. Resources. [1]

Technical Review 28

Technical Review 2005 Estimate Software Review 28

Herding Cats

JANUARY 17, 2017

Barry Boehm's work in “Software Engineering Economics”. This is due to many reasons. We have a target weight at Test Readiness Review of 23KG. 2] System Analysis, Design, and Development Concepts, Principles, and Practices, Charles Wasson, John Wiley & Sons. [3] Software Engineering Economics”. Resources. [1]

Technical Review 28

Technical Review 2005 Estimate Software Review 28

Herding Cats

MARCH 11, 2018

Microeconomics is applicable to the development is software systems. If we look at the discipline of software engineering, we see that the microeconomics branch of economics deals more with the types of decisions we need to make as software engineers or managers. Software engineering economics." Boehm, Barry W.

Software Developers 34

Software Developers Software Development Risk Management Risk 34

Scrum.org

AUGUST 3, 2020

Dependencies are an epidemic in software development. Sutherland, Scrum Guide, 2013. Thing we hear (or say): Organizational Design: My team is mostly back-end; we rely on another team for the (fill in with any component of software – front end enhancements, database layer, integration, API). Schwaber and J.

Underperforming Technical Team 242

Underperforming Technical Team Technical Review Software Review Development Team Review 242

Herding Cats

FEBRUARY 4, 2017

Barry Boehm's work in “Software Engineering Economics”. This is due to many reasons. We have a target weight at Test Readiness Review of 23KG. 2] System Analysis, Design, and Development Concepts, Principles, and Practices, Charles Wasson, John Wiley & Sons. [3] Software Engineering Economics”. Resources. [1]

Technical Review 28

Technical Review Estimate 2005 Software Review 28

Scrum.org

APRIL 7, 2022

Wang et al (2006) studied software teams tasked with ERP implementations and found that cohesive teams performed significantly better than less-cohesive teams. However, several studies show that cohesion positively impacts performance only in later stages of team development (e.g. Bradley et. Or if these processes can be fast-tracked.

Underperforming Technical Team 174

Underperforming Technical Team 2007 2006 2009 174

MPUG

APRIL 29, 2020

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 technical category and the MPUG activity code for claiming this session is on the screen now.

Estimate 52

Estimate Software Review Risk Management Risk 52

Scrum.org

AUGUST 17, 2020

When comparing different approaches to develop software, survival bias can lead someone to conclude that plan-driven approaches work well based on a few success stories they have where they did. All drivers consider their own driving skills above average (Roy & Liersch, 2013). Psychological Review, 94 (2), 211–228.

2015 224

2015 2014 2004 Influencer 224

Wrike

NOVEMBER 7, 2018

Project Management Software & Tools. Lean & Test Driven Development (TDD) – 11%. Feature Development Driven – 9%. Dynamic Systems Development Method – 3%. Project Management Software & Tools. Most-Wanted Features in Project Management Software: 1. 53% use project management software.

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

Teamweek

JUNE 25, 2020

According to a 2013 Harvard Study , employees spend 41% of their time on unproductive work. Here’s a review from SoftwareAdvice that sums up the frustration that teams have Asana. This Asana review on G2 , describes how frustrating it is to navigate across Asana’s features. Ease of use. Today it’s even worse.

Underperforming Technical Team 97

Underperforming Technical Team Software Review Planning Development Team Review 97

Leading Agile

DECEMBER 17, 2018

I didn’t realize James Bond was into software development. ” Figuring out exactly where included code comes from is a Good Thing®. Everyone can have code that looks the way they like it to look. I didn’t really expect anything to come of the tweet, and I was a little surprised at the responses.

Underperforming Technical Team 77

Underperforming Technical Team Software Review 2008 2013 77

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. Chakraborty and K.

Estimate 40

Estimate Software Review Software 2012 40

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

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

Herding Cats

NOVEMBER 5, 2018

In software development, those managing the project have some understanding the market forces (from their marketing departments), the technology (from their engineering department), and how to manage in the presence of Aleatory and Epistemic risk (the managers running a successful firm). Software projects are non-ergodic.

Software Review 34

Software Review Technical Review Estimate Software Developers 34

MPUG

NOVEMBER 14, 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. And you get asked a question to enter a code. And this code is 18 11 17. And to be honest, I haven’t used it since 2013. So, where did that go?

2013 40

2013 Finance 2007 Software Review 40

Herding Cats

NOVEMBER 7, 2016

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. The Future of Systems-and Software Development. Springer International Publishing, 2016.

Estimate 64

Estimate 2006 2005 2013 64

Herding Cats

JUNE 21, 2016

Here's another trail being ridden by our son at Nationals in 2013. The notion of Control is missed used in software development projects. What's coming due? When riding a single track like this one behind our neighborhood, I came to an understand of the tradeoffs between stability and control. Misused and misunderstood.

Controlling 42

Controlling Technical Review Estimate 2013 42

International Institute for Learning

SEPTEMBER 20, 2022

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]. Martine Haas and Mark Mortensen, “The Secrets of Great Teamwork”, Harvard Business Review, June 2016. 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.

Technical Review 43

Technical Review 2010 Estimate Software Review 43