Tutorials and tools for managing, estimating, planning and tracking software development projects: PMP, Agile, Scrum, Lean, Kanban
As you advance in your software development career, your responsibilities evolve from being a junior to a senior, project manager, architect, or scrum master. How does this transformation affect your daily duties, and what value do you bring to the project team? Can your software development team function efficiently without...
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 video offers advice on leading software development teams. How do you make the step from software developer to manager? How do you deal with difficult situations and conversations? What are some of the commonest mistakes that people starting out in team leadership often make?
This article originally contains a list of resources about the most valuable positions, roles and responsibilities in a software development team. The original content mentioned had disappeared, so you will find below another list of resources about the how to form the best software development teams and what are the...
In this article, based on chapter 4 of MongoDB in Action, author Kyle Banker explains how MongoDB schema differs from an equivalent relational database (RDBMS) schema, and how common data model relationships between entities, such as one-to-many and many-to-many, are replicated in MongoDB.
When we look at the software that needs to be developed we have people pushing us to make sure we get the feature out as fast as possible. However, this will generally have an impact on the quality of the software that is being developed.
Good requirements are the foundation of software development projects. It is more important to “do the right thing” than to “do things right”. The book “So You Want To Be A Scrum Master?” discusses the impact of poor requirements in software development and why people are the main issue.
Nowadays, it is pretty hard to find an application that doesn’t have a data flow that depends on external services, such as databases, queues or caches. We could also include API services in the mix, if it is a third-party service.
Getting the balance right between often opposite and interconnected forces of decoupling and collaboration, when it comes to deciding on software development team boundaries for happy and effective teams, is as much and art as it is a science.
With DevOps being a state-of-the-art mindset, we find ourselves with autonomous software development teams who can take full ownership and not only develops features but also follow up on their usage, put them in production and fix them when they break.
Why should we keep software soft? Because software should be easy to change. This is how this book from Jason Roberts starts. In the first page of the book Keeping Software Soft – A Practical Guide for Developers, Testers, and Managers, he writes “If you want to make developing software...
