Scrum.org

AUGUST 1, 2022

It has been linked to higher performance and motivation (Mathieu et al, 2000), increased effectiveness (Kearny, Gebert & Voelpel, 2009), and generally explains a substantial amount of the variance (~19%) in the effectiveness of teams (De Church & Mesmer-Magnus, 2010). Analysis of fault generation caused by stress during software development.

2004 228

2004 2010 2009 2016 228

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

APRIL 7, 2022

Research has linked team cognition to higher performance and motivation (Mathieu et al, 2000), increased effectiveness (Kearny, Gebert & Voelpel, 2009), and generally explains a substantial amount of the variance (~19%) in the effectiveness of teams (De Church & Mesmer-Magnus, 2010). Bradley et. Or if these processes can be fast-tracked.

Underperforming Technical Team 162

Underperforming Technical Team 2007 2006 2009 162

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). Fitzgerald, B (2009). Creativity in agile systems development: a literature review.

Innovation 59

Innovation Agile 2002 2001 59

Herding Cats

OCTOBER 30, 2018

There have been some recent posts about managing scope, defining needed Features, determining how to release software to stakeholders - in both traditional and agile processes. This document is all but unknown in the Enterprise IT domain and completely unknown in the agile software development world.

Planning 109

Planning 2007 Technical Review 2009 109

The IIL Blog

MAY 17, 2023

Most contractors solved the problem by creating technical writing departments that reviewed all reports prepared by PMs before sending them to the clients. Executives attended project review meetings with the government agencies to make it appear that they were functioning as active sponsors rather than as invisible sponsors.

Aerospace 147

Aerospace Technical Review Underperforming Technical Team Governance 147

Digite

JANUARY 7, 2018

This is the original book where David Anderson first laid down the definition of and guidance to the Kanban Method for software and knowledge work. This is the original book where David Anderson first laid down the definition of and guidance to the Kanban Method for software and knowledge work. By David J Anderson. By Mike Burrows.

Lean 79

Lean Software Review 2010 2014 79

Herding Cats

OCTOBER 5, 2018

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 ? This variation can be explained by the fact that initial concepts do not describe the final software system accurate enough.

2012 48

2012 2007 2011 2010 48

Leading Agile

NOVEMBER 17, 2020

And in that we grew the company where originally, we did a mixture, as you know, between transformation and building custom software solutions. Over time, we grew to focus more, mainly on customer soft, custom software solutions, and eventually Accenture purchased us. So— – We reconnected, yeah. – Interesting.

Technical Review 78

Technical Review Software Review Agile Governance 78

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

EasyProjects

SEPTEMBER 24, 2019

If you follow the instructions to a tee, it’s going to taste fantastic – just like the reviews say. Agile is most popular in the software industry, but it has found homes in the information technology, engineering, product development, and marketing industries to name a few. Deliver code that is extensible.

Agile 41

Agile Technical Review Software Review Underperforming Technical Team 41

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 2011 2015 46

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). Dallas MPUG , May 6th, 2009.

Technical Review 42

Technical Review Performance Measurement Government Governance 42

Online PM Courses

SEPTEMBER 16, 2018

In 2009 Ken Schwaber left Scrum Alliance to build his own Agile certification, PSM (Professional Scrum Master), at scrum.org. The Scaled Agile Framework (SAFe®) is a methodology that focuses on developing and delivering enterprise-class software and systems as quickly as possible. And we also offer access to the exam.

Certification 140

Certification Agile Prince2 PMI 140

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. Software Engineering Economics”. Software Cost Estimation with COCOMO II, Prentice-Hall, 2000. [10] Software Sizing, Estimation, and Risk Management, Auer-bach, 2006. [15]Jorgensen,

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. Software Engineering Economics”. Software Cost Estimation with COCOMO II, Prentice-Hall, 2000. [10] Software Sizing, Estimation, and Risk Management, Auer-bach, 2006. [15]Jorgensen,

Technical Review 28

Technical Review 2005 Estimate Software Review 28

MPUG

SEPTEMBER 9, 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 the Technical category, and the MPUG Activity Code for claiming is on the screen now.

Software Review 52

Software Review Critical Chain Technical Review Risk Management 52

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. Software Engineering Economics”. Software Cost Estimation with COCOMO II, Prentice-Hall, 2000. [10] Software Sizing, Estimation, and Risk Management, Auer-bach, 2006. [15]Jorgensen,

Technical Review 28

Technical Review Estimate 2005 Software Review 28

Wrike

APRIL 12, 2016

In his conversational writing style, he tackles the parallels between software development and marketing, walks you through the workflows and best practices behind Agile marketing, and lays out everyday tactics for managing the entire marketing process successfully. Snapchat) as well as an entire chapter on sales & service.

2014 36

2014 2015 2016 Technical Review 36

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

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. 5887, 2009. A Critical Review Of Risk Management Support Tools,” Irem Dikmen, M.

Risk Management 38

Risk Management Risk Technical Review 2002 38

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

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

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. There may be exclusions, such as those steps included in product demonstrations.

2013 40

2013 Finance 2007 Software Review 40