2007 2018 Software Review Technical Review 
Scrum.org
DECEMBER 23, 2021
Why is code quality so often an issue? Why do software teams?—?despite So I was pleasantly surprised when Carsten Grønbejrg Lützen pointed at a peer-reviewed academic paper by Michele Tufano and his colleagues (2015), called “When and Why Your Code Starts To Smell Bad”. Technical Debt and Code Smells.
Scrum.org
APRIL 7, 2022
This concern is also present in academic literature, where authors like Mathieu and his colleagues (2008) and Mortensen and Haas (2018) point out that there is a research gap because studies are often based on stable teams, whereas this is often not the case in the modern workplace. This effect is stronger for smaller teams than larger teams.
This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
ProjectManager.com
DECEMBER 12, 2018
In 1969, in Philadelphia, Jim Snyder, of Smith, Kline & French Laboratories, and Gordon Davis, of the Georgia Institute of Technology, were having dinner and decided there was a need for an organization that offered project managers a forum to share information and discuss their industry. Certification.
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. I will explain the peer review at the end of this article.
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. Performance Evaluation of non?Markovian
Planio
JULY 22, 2020
The Culture Code: The Secrets of Highly Successful Groups. Swipe to Unlock: The Primer on Technology and Business Strategy. Technical documentation. Each chapter ends with quick reviews making this a useful “PMBOK for Dummies”. Author: Harvard Business Review. Influence: The Psychology of Persuasion.
Herding Cats
MAY 10, 2019
Information about key project cost, (technical) performance, and schedule attributes is often uncertain or unknown until late in the program. 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.
Expert insights. Personalized for you.
174 
Let's personalize your content