2014 Groups Influencer Software Development 
Scrum.org
AUGUST 1, 2022
For example, teams could agree to a time-out and a group conversation. Many studies have found that psychological safety has a positive influence on team effectiveness (Edmondson, 2014). Analysis of fault generation caused by stress during software development. In Achieving Quality in Software (pp.
Project Pulse Journal
APRIL 8, 2024
Each approach establishes the development of project deliverables as influenced by the delivery cadence, defined as the number and timing of deliveries based on the type of deliverable. Understanding the influence of external factors allows modification of the chosen approach to meet external challenges head-on.
This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
Herding Cats
MARCH 17, 2019
Integrated Master Plan: The Foundation of Program Success , College of Performance Management, May 21, 2014. Agile Software Development for Government Software Intensive System of Systems (SISoS) , Boulder Agile Meetup, 27 July 2016. Product & Process Development Kaizen , LPPDE, Denver, Colorado, April 21-23, 2008.
Scrum.org
OCTOBER 19, 2022
Throughout this post, we define them as “all users, customers, and other people or groups who have a clear stake in the outcomes of what this team produces, and invest money, time or both in making sure that happens”. 2014 ; Young & Jordan, 2008 ; Russo, 2021 ). Journal of systems and software , 81 (6), 961–971. 2013, June).
Herding Cats
MAY 10, 2019
“A Taxonomy of Threats for Complex Risk Management,” Centre for Risk Studies, Research Programme of the Cambridge Centre for Risk Studies, University of Cambridge, Judge Business School, June 2014. “A IEEE Transactions on Software Engineering , Vol. 1, March 2014. 5, September/October 2011. 255, April 2010. 920, November 2004.
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.
Scrum.org
AUGUST 17, 2020
This series is not about easy answers or practical tips, but to develop a more complete understanding of what may be going on. So whenever you or a group you are with needs to validate an assumption or a belief, also consider what you’d need to see to challenge that belief. Learn how the impact of eight common biases?
Expert insights. Personalized for you.
227 
Let's personalize your content