Project Management for Software Development
Tutorials and tools for managing, estimating, planning and tracking software development projects: PMP, Agile, Scrum, Lean, Kanban
I must admit that I was initially a little bit skeptical on a book about agility coming out from IBM. I was wrong. Although you will find a little bit of “bigblueness” in the content, I really enjoy reading “The Jazz Process” that proposes a deep and interesting perspective on...
A Gantt chart is a type of chart that shows the schedule of a software development project. Gantt charts show the dependency relationships between activities and the current schedule status. They provide a big picture of the plan and the realization of projects, including the critical path. This chart was...
The book “Managing the Unmanageable” starts with the observation that software development projects have always difficulties to be successful, which might explain the title of this book. The authors share in it some techniques and approaches to improve this situation, based on their long experience as software development managers in...
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?
Sometimes, it is not possible to keep a team member who is causing problems for your software development project. In their book “Managing the Unmanageable”, Mickey Mantle and Ron Lichty provides advice to the project manager on how to dismiss a person who is not performing well or who demonstrates...
Certifications are helpful to improve professional careers. Various business analysis and software requirements organizations exist that offers both a community for sharing knowledge and certifications opportunities, similarly than the Project Management Institute provides for project management domain with its PMP program.
Specification by Example by Gojko Adzic is a book that provides a set of process patterns that facilitate change in software products to ensure the right product is delivered effectively. This book about software requirements is based on the research of 30 teams that implemented 50 projects.
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.
Last Comments