2010 Software Review Technical Review Underperforming Technical Team 
Rebel’s Guide to PM
APRIL 12, 2023
During a company integration program, customer service levels dropped by 25-50% because the team management focused their efforts on reorganizing and changing employees’ roles and responsibilities, all with “the best of intentions”. For example, in June 2010 Chrysler merged with Fiat. So why do some projects crash to their doom?
Wrike
MAY 23, 2023
I joined the team as a QAA engineer in 2010, the first employee in this role. Over the past 12 or so years, we have built a super team of brilliant QAA engineers. As our client base grew, so too did our responsibility to ensure high-quality product code. But he was wrong — Team Sky won in just three.
This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
Scrum.org
DECEMBER 23, 2021
Each post discusses scientific research that is relevant to our work with Scrum and Agile teams. Why is code quality so often an issue? Why do software teams?—?despite But also a field that has much to say about code quality and how we can be better developers. Technical Debt and Code Smells.
Herding Cats
MAY 10, 2019
Risk Management is essential for development and production programs. Information about key project cost, (technical) performance, and schedule attributes is often uncertain or unknown until late in the program. IEEE Transactions on Software Engineering , Vol. 255, April 2010. Risk Management Papers. “A 3, March 2002.
Project Pulse Journal
MAY 20, 2024
Everyone dreams of working on a project where every team member is in harmony, there are fewer misunderstandings, and progress is communicated clearly and consistently through well-established communication channels. Are you tired of project delays and misunderstandings caused by poor communication?
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.
The Lazy Project Manager
MAY 5, 2016
It also seems that there is a preference to have talks with broad appeal, this, I feel, has led to a reduced number of more technical talks on advanced topics. The ones I attend are the ones with good speakers… IPMA in particular has a very poor choice of speaker. So what is my concern and why am I mentioning PMI?
Expert insights. Personalized for you.
426 
Let's personalize your content