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.

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

In outlining the elements that encourage the design of a humane UX practice, we considered current and future states, an academy of learning, values and beliefs, the language that a project team uses, toolkits; soft skills, or human qualities that deserve continuous practice; spaces in which to design and validate solutions, learnings from stories; and well-understood, shared artifacts for members of project teams to use in telling their common story, independent of their role on a project.

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.

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.

Like the notion of technical debt, the concept of management debt relates to the leadership issues that prevent a successful Agile transformation. This article from Agile transformation expert Sriram Rajagopalan discusses the types of waste that can be eliminated using a Kanban approach and the role of management debt in perpetuating wasteful practices.

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.

This article talks about Good, Bad, and Ugly ways to negotiate, with an eye toward how a project manager might use these in the complex and sometimes confusing "real world."

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.