Project Management for Software Development
Tutorials and tools for managing, estimating, planning and tracking software development projects: PMP, Agile, Scrum, Lean, Kanban
In a period where the trend is to follow agile approaches with condensed guidance (see the 12 principles of the Agile Manifesto for instance), it could seem strange to publish a book on software development with more than 500 dense pages. You should however not be frightened by the book...
The Incremental Commitment Spiral Model (ICSM) book is based on the initial work of Barry Boehm about the Spiral Model in 1988. According to the authors, ” Most of the problems in using the 1988 spiral model stemmed from users looking at the diagram and constructing processes that had nothing...
In an era where managing requirements could seem to be limited to writing user stories with a “as a … I want … so that” format on a post-it, it could be strange to publish a 500 pages book on this topic. However, people that want to improve their knowledge...
The book “Lean Integration” by John G. Schmid and David Lyle is the sequel of a first book titled “Integration Competency Center: An Implementation Methodology” and is aimed at taking it “to the next level by adding more specific best practices and a rich collection of case studies”. The book...
The late Watts S. Humphrey has been an important personality of the software development world. He led the development of the Software Capability Maturity Model (CMMI), an internationally recognized standard in the field of software process improvement. The title of his last book “Leadership, Teamwork, and Trust – Building a...
In the category of project management books, the book “Adaptive Project Framework” is a little bit different, as its goal is to present an open framework and not a prescriptive model. As the author Robert K. Wysocki wrote, many project managers prefer to apply an existing recipe for their project.
If you want to build a relationship of trust with the team, behave showing the example that you want the team to follow. That means, be present physically and mentally 100% of the time.
With the adoption of Agile approaches for software development projects, technical debt has become a trendy term for an issue that exists since the beginning of programming. Software debtis what happens when you neglect, consciously or not, the long-term quality of your software to achieve other usually short term benefits.