Tutorials and tools for managing, estimating, planning and tracking software development projects: PMP, Agile, Scrum, Lean, Kanban
Collaborating on deriving scope from goals is undoubtedly the most controversial topic in this book. In the last five years, the surge in popularity of value chains in software development has increased awareness of the idea of collaborating on scope and deriving it from business goals.
Think of the times when you have to collaborate with business units, cross-departmental teams, and other functions. Too often, complex ideas and jargon can impact cross-departmental communication and collaboration effectiveness and efficiency.
In the Agile world, bottom-up continuous improvement is the new mantra that replace the (rarely done) postmortem reviews of traditional project management approaches used in software development.
Communicating software architecture is a crucial aspect of being a successful software architect, however, this is a skill you don’t get taught. Learning by trial and error is not ideal, so how do you create inclusive diagrams and visuals that successfully communicate to your audience?
This article contains a selected list of free and open source project management software tools that can be used to manage software development projects. The features provided by traditional open source project management tools are the Work Breakdown Structure (WBS), the Gantt and PERT charts, Critical Path Management (CPM) to...
This article explores the concept of resiliency in software development and project planning. Resiliency is defined by the capability of an application to recover to a stable, functioning state after failure or adverse events.
This presentation explains how mindfulness enables software development teams, and individuals, deal with stress and cope with burnout. Mindfulness helps us to think more clearly, remain focused and handle challenges with more ease.
Conway’s law describes the link between communication structure of organizations and the systems they design. It is named after the computer scientist and programmer Melvin Conway, who introduced the idea in 1967: “[O]rganizations which design systems (in the broad sense used here) are constrained to produce designs which are copies...
The Process of Software Architecting is a book that presents the influence of architecture in the software development process. The interesting aspect of this book is that is it a thorough presentation of the architecture role in the software development activities, not only at the initial analytic stage but also...
The conversation challenges traditional governance models, advocating for hypothesis-driven product management and continuous feedback mechanisms to deliver quality software.
Working software over comprehensive documentation is one of the key element of the Agile Manifesto. In his book “Software Ownership Transfer”, Vinod Sankaranarayanan provides his perspective on why software documentation should not become an objective in itself for software development projects.
Last Comments