How long does it take an organization to reorganize in order to adopt Scrum? Three hours. Really.

Have you ever been on a project where some person or group is holding up the works? They are called the “bottleneck” station, and here are some usual and unusual strategies for improving output in the presence of various bottlenecks.

The systems development life cycle (SDLC) is a conceptual model used to develop information systems with well-defined phases. The phases are: user requirements definition, system requirements definition, analysis and system design, system development, testing, implementation, and maintenance. Some of the models used are Waterfall, spiral, and rapid prototyping. These models are called plan-driven, lying on one end of the "planning emphasis" continuum. At the other end of the continuum are the Agile methods, which are considered adaptive rather than predictive. This paper presents a systems-theory perspective of both models, including the inherent challenges that need to be addressed when transitioning from traditional to Agile methods.

In this second and final part of our article on self-selecting teams, you will learn how to get your self-selection event off the ground. We will also provide tips on how to get the most out of it and keep the momentum going afterwards.

We can all agree that shared responsibilities are important on a project, but we should also have clear accountability. Someone must ultimately be answerable for the correct and thorough completion of the deliverable, and that should be a unique individual.

Lean how to improve communication in distributed software development teams.

Stakeholders are individuals or organizations who stand to gain or lose from the success or failure of a software development project. This article focuses is on internal stakeholders within the organization and the need to prioritize between them to create the good requirements for a successful project. It presents a process for dealing with internal stakeholders and tools to help prioritizing them.

This article hopes to help you become a better dancer by exploring some of the principles of agile interactions that I have seen play out on a number of scrum teams. More specifically, we will focus on those interactions necessary to discovering and elaborating requirements within the context of the Scrum framework.

Marathon training and product development have a lot of similarities. They should be both treated and executed as time bound and goal oriented projects. To be successful, you need a lot of flexibility, introspection and continuous improvisation.

The information and communications technology (ICT) world is “addicted” to dysfunctional behavior and the problem is spreading globally. The sad truth is that the parties in the ICT relationship (the customer and the supplier) are largely co-dependent on a pattern of dysfunction characterized by ineffective communication, fixed price contracts with changing requirements, and eroding trust. This article focuses specifically on the northernSCOPE TM 12-step process for ICT program recovery.