Effecting Change: How To Leading Software Development Teams
As project managers, we want our software development teams to pursue great ideas and change directions to realize the goals. However, often we find it hard to implement changes.
Project Management for Software Development
Tutorials and tools for managing, estimating, planning and tracking software development projects: PMP, Agile, Scrum, Lean, Kanban
As project managers, we want our software development teams to pursue great ideas and change directions to realize the goals. However, often we find it hard to implement changes.
The software development project manager has been working hard to meet a deadline and then he receives an email from your boss, asking him to take on a new project. He is e at capacity with his time, resources, and focus, but he still feels obliged to say “yes”.
The easier designs are to use, the less users tend to think about the work that went into making them that way. We know good designs are largely the result of your careful efforts during softgware development projects.
Unfortunately, the majority of data projects fail. Yet, they fail for the same reasons. Most management and data teams don’t know the reasons a project succeeds or fails. It just appears to be random, hard work, or luck.
Adaptive/Lean Portfolio Management (LPM) is key to effectively becoming an agile organization and can be considered one of the pillars of business agility. In this presentation, Shane Hastie introduces the key ideas around LPM, discusses the 12 principles of Lean Portfolio Management.
Human beings suck at committing anything, even if this is an important part of software development project planning. That is – the committing part is easy, fulfilling the promises – not anymore. Anger, frustration, disappointment – sounds familiar?
Traditional project management wisdom teaches us that long-lived, stable teams perform best, and that changing team membership is to be avoided as much as possible. Redgate Software has challenged this advice, believing it was better for software engineers and the overall organization to deliberately change-up our teams every year.
Working in collaborative, self-organizing Agile software development teams can be challenging. It is important that all team members understand the group dynamics involved and how to effectively facilitate these sessions.