2006 2019 Influencer Software Development 
Scrum.org
APRIL 7, 2022
Kozlowski & Ilgen (2006) describe this reciprocity as “process begets structure, which in turn guides process”. Wang et al (2006) studied software teams tasked with ERP implementations and found that cohesive teams performed significantly better than less-cohesive teams. In turn, this facilitates further collaboration.
Planio
JULY 22, 2020
Influence: The Psychology of Persuasion. 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. Published date: 2019 (Updated edition). Influence: The Psychology of Persuasion.
This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
Herding Cats
MAY 7, 2019
Effort Distribution to Estimate Cost in Small to Medium Software Development Project with Use Case Points,” Putu Linda Primandari and Sholiq, The Third Information Systems International Conference, Procedia Computer Science, 72, pp. COSMIC Software Estimation Approach,” Alain Abran, ICEAA Workshop, Portland Oregon, June 6?9,
Herding Cats
MAY 10, 2019
México, 1 al 3 de Febrero de 2006. Taxonomy-Based Risk Identification,” Marvin Carr, Suresh Konda, Ira Monarch, Carlo Ulrich, and Clay Walker, Technical Report, CMU/SEI-93-TR-6, Software Engineering Institute, June 1993. Pich, Working Paper, 21/2006, Cambridge University, Judge Business School. 85 1 Feb 2019. “An
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. México, 1 al 3 de Febrero de 2006. De Meyer, C.
Expert insights. Personalized for you.
163 
Let's personalize your content