Author: Project Management Planet

alt text

Specification by Example

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.

Four Years of Team Self-Selection at Redgate Software

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.

From Good to Great: Agile Team Facilitation

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.

People as the Source of Business Agility

Successful Agile businesses such as Spotify and Netflix have become the example for those on a business agility journey. The secret ingredient they all share… people… more specifically, a mission built around people.

project management group people

User Stories for Both Requirements and Testing

User stories are a technique taken from the agile development playbook that can easily be applied in traditional systems development and maintenance. User stories help you document needs in a structured way, from the users’ perspective.

Why is Coffee Important in Software Development Projects?

Why is Coffee Important in Software Development Projects?

We have all heard of phrases such as “Let’s walk and talk”, “Give me your elevator pitch” or “Let’s get a coffee”. When someone comes up to you and says “let’s get a coffee”, you instinctively know that you are about to have a conversation with this person.