2012 Influencer Software 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.
The IIL Blog
JULY 31, 2024
Align with the Business Need A Guide to the Project Management Body of Knowledge ( PMBOK ), the bible for project managers, states that “projects are initiated due to internal business needs or external influences”. Many software tools are available for recording and tracking requirements. Denver, Colorado, 25 April, 2018.
This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
ProjectManager.com
AUGUST 29, 2019
Influence and persuasion start with confidence. But I do like the reframe that Amy Cuddy offers in her 2012 TED talk , which has garnered of 52 million views, as I write this. Even if some tasks fall behind, you can easily drag and drop the timelines to adjust due dates and reassign workload. I don’t like this.
Rebel’s Guide to PM
MARCH 23, 2022
This is an edited extract from my book Customer-Centric Project Management , co-authored with Phil Peplow (Routledge, 2012). For example, the Sales Director would sponsor a project to install new customer management software, providing the sales team with more opportunities to cross-sell to the existing customer base.
Rebel’s Guide to PM
AUGUST 6, 2022
In every case, you should have people on the group who understand the project (or who can be brought up to speed) and who have influence and interest in the outcomes. Action review and next steps. Set up a meeting with your sponsor to review roles and responsibilities and agree the terms of reference for the group(s).
Scrum.org
FEBRUARY 3, 2020
Software development is (generally speaking) very complex. Why our brain is not built for software engineering. So, answering your mail and writing some code at the same time is going to decrease productiveness. Nevertheless, the motto of software development is often ‘first solve the problem, then write the code’.
Scrum.org
APRIL 7, 2022
Edmondson (2012) argues that dynamic teaming is important to share and encourage learning. This is also what inspired Edmondson (2012) in her academic work on “teaming”. They also tend to perform better (Evans & Dion, 2012), are better able to deal with stress and pressure (Salas, Driskell & Hughes, 1996). Bradley et.
Expert insights. Personalized for you.
226 
Let's personalize your content