Have you ever worked in a superteam? The kind of team where the process is the natural flow of the team. Everyone on the team working on his or her parts of the project and it all comes together as one perfect whole. Discussions flow easily, decisions get made and
In real world agile teams, traditionally defined rigid roles are rapidly being displaced by a culture of collective ownership of the product. Responsibilities are being decoupled from specialties by a collection of operators with overlapping skills, and chief among them is technical acumen.
This video discusses the four values of Agile: responding to change over following a plan, customer collaboration over contract negotiation, working software over comprehensive documentation, individuals and interactions over process and tools.
This article describes a recent experience with a software development project trying to adopt the Agile methodology without enough guidance. This methodology is then compared with the traditional Waterfall approach, the potential advantages and pitfalls of both being compared. It is assumed that readers have basic understanding of both methodologies.
Focussing on empowered professional software engineers, well defined testing strategy, process automation, high investment in people development, requirements management and strong emphasis on quality.
As Agile approaches like Scrum are supposed to be dominant for enterprise software project management, the latest Methods & Tools survey asked the following question: Which project management approach is used by your project? The results make us think that the situation is a little bit more complex than the
ScrumButs are defined as reasons why teams cannot take full advantage of Scrum to solve their problems and realize the full benefits of product development using Scrum. A ScrumBut retains the problem while modifying Scrum to make it invisible so that the dysfunction is no longer a thorn in the
Agile methods in general have arise from a mixture of sound practice and good principles, but they lack an over all theory. Complexity Science, coupled with insights from the Cognitive Sciences challenges the basic assumptions of systems thinking and idealist uses of “self-organisation” alike.
As Agile adoption is spreading and more software development teams want to adopt an Agile project management approach like Scrum. In this article, Robert Karlsson ask the question the question “Why should your boss let you implement Scrum in your organization?”. Your boss might be satisfied with the current situation
Managing traditional or Scrum project performance is never easy. This talk aligns two different ways of doing it, the Agile and the traditional. Traditional project management is based on the mostly used project management standard, the Project Management Body of Knowledge (PMBOK). This is not a presentation of Agile and