2002 Leadership Software Development Technical Review 
Epicflow Blog
MAY 14, 2019
Over 200 PM experts from ExxonMobil, INEOS, DXC Technology, and other companies have shared their experience and proved that it’s a super hot topic. Business drivers have to be translated into project drivers by a strong technical team, not management. Develop Your Leadership Skills.
Planio
JULY 22, 2020
Swipe to Unlock: The Primer on Technology and Business Strategy. The best books for crafting your leadership qualities. True North: Discover Your Authentic Leadership. The Five Dysfunctions of a Team: A Leadership Fable. Technical documentation. Author: Harvard Business Review. Principles: Life and Work.
This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
Herding Cats
APRIL 16, 2019
Business, Technical, Systems, Risk, and Project Management Briefings and Presentations. Technical Performance Measures (#TPM). Cost, Schedule, and Technical Performance Management (#CSTPM). Product Development (#ProdDev). Agile Software Development (#ASD). Table of Contents (Click the Name to go to Section).
Leading Agile
FEBRUARY 11, 2019
When I first learned about Agile methods in 2002, the principles seemed to offer an ideal solution to many organizational issues common at the time. How can the same principle be a good idea in 2002 and a bad idea in 2019? As a result, the organization never benefited from the full potential of the technical staff. Stable Team.
International Institute for Learning
SEPTEMBER 20, 2022
Managing a team is definitely something really difficult because in addition, for instance, to the technical complexity of the topic, there is the challenge to coordinate people with different personalities, knowledge, background and even culture with the purpose of making the team work in an efficient way. Schwaber, K. Hackman, J.
Expert insights. Personalized for you.
75 
Let's personalize your content