Category: Scrum

Colocation is useful for meetings that require close listening, such as design discussions. It is also handy when new employees are training and need some amount of hand-holding or encouragement. Whiteboard is highly effective for colocated team but can be managed with online tools as well.

Release early, release often is a software development philosophy that emphasizes the importance of early and frequent releases in creating a tight feedback loop between developers and testers or users, contrary to a feature-based release strategy.

Not all items in the product backlog will be of the same size and level of detail (i.e. features/ eprics/ user stories and tasks) at the same time. PBIs that we plan to work on soon should be at the top of the backlog, smaller in size, and very detailed so that they can be worked on in the near-term sprint. PBIs that we won’t be working on for some time should be at the bottom of the backlog, larger, and less detailed.

A vision statement identifies where the organization wants or intends to be in future or where it should be to best meet the needs of the stakeholders. Every project needs a vision to steer itself in a proper direction. A vision serves as a guide for choosing the current as well as future course of actions.

What is Predictive Process? A defined and predictive process model is appropriate if both the requirements for the project and

Cynefin Framework helps managers to identify how they perceive situations and make sense of their own and other people’s behavior. It draws on research into systems theory, complexity theory, network theory and learning theories.

A Product Owner is responsible for telling what should be developed and the order of items that needs to be fulfilled. You can consider him as the sole authority that would tell the rest of the team what they need to create and which features should come first. In short, he is the one who tells the other members of the team about what they should be coming up with.

Scrum is a framework for developing and maintaining complex products and is an incremental, iterative development process. In this framework, the entire development process consists of several short iteration cycles, a short iteration cycle called a Sprint, and each Sprint is 2 to 4 weeks long.

The history of the Scrum method starts in 1986. That year, two Japanese business experts introduced the term in the context of product development. Hirotaka Takeuchi and Ikujiro Nonaka published the article, “New New Product Development Game” (the double “New” is indeed part of the title) in the Harvard Business Review. The authors described a new approach to commercial product development that would increase speed and flexibility. Their inspiration came from case studies from manufacturing firms in the automotive, photocopier, and printer industries.

Product owner — holds the vision for the product; Scrum Master — helps the team best use Scrum to build the product; Development team — builds the product