Helpful resources for today's leaders
Today, more than ever, organizations need to build products that add higher value to customers and the business. To be more competitive, companies need to develop products in a faster way by reducing costs. To accomplish this goal, organizations can use the Nexus framework, to scale software and product development. …
In Scrum, the Product Backlog Items are refined, during the activity of “Backlog Refinement”, until they are “Ready” for selection in Sprint Planning. To determine the items that are ready it is important that Scrum teams consider “Definition of Ready”. In fact, the Definition of Ready helps Product Owners to …
There are companies that use Nexus to scale their software and product development. Nexus is a framework based on Scrum that uses an iterative and incremental approach to develop products. Nexus is based on the Scrum Framework and increases Scrum slightly. Let’s see why Nexus is based on Scrum and …
Many companies in the software industry have to often deal with the concept of “technical debt”. Technical debt is also known as design debt or code debt. Let’s analyze this concept in depth. What is technical debt? Technical debt happens when development teams take actions to expedite the delivery of …
The Nexus framework is based on Scrum. It helps companies to scale software and product development. In fact, it helps organizations to develop products in a faster way by reducing costs. Let’s analyze in depth two Nexus events: Nexus Sprint Review and Retrospective. What is the Nexus Sprint Review? The …
Many Scrum teams use Kanban to organise their project work. In fact, these teams use Kanban as a visual management tool to deliver work faster and more often. Let’s see what is Kanban and how it is evolving over time. What is Kanban? Kanban is a lean method that aims …
Nexus helps companies to scale software and product development. In fact, thanks to this framework organizations are able to develop products in a faster way by reducing costs. As the Nexus framework is based on Scrum, it can be useful to understand what are the differences between Scrum and Nexus. …
To develop a new product with Scrum it is important to turn requirements into working functionalities. In fact, the development team has to turn product backlog items into working product features. To be successful, you need to convert the list of product features, contained into the product backlog, into a …
Scrum does not clearly define any controls. As Scrum is a risk-reduction framework it already contains various risk controls. In fact it is important to remember that Scrum aims at solving complicated issues to reach project success. Here is a list of controls that can reduce the risk of project …
Nexus is a framework, based on Scrum, that helps companies to scale software and product development. In fact, thanks to this framework organizations can plan, launch, scale and manage large product and software development projects. In addition, they are able to develop products in a faster way by reducing costs. …
Scrum is a framework that implements an empirical process. In general, empiricism is a principle that states that to obtain knowledge people should depend on practice and experiments, rather than on theories. In fact, thanks to this process, progress is based on observations of reality and not on imaginary plans. …
To be more competitive today companies need to develop products in a faster and cheaper way. To achieve this goal they necessarily need to scale the product development process. In fact, they can use the Nexus framework, which is based on Scrum, to manage large and complex product development projects. …
To estimate Product Backlog items Scrum does not require a specific technique. The objective of estimation Estimations should allow discussion to obtain more information about the product backlog items. Estimations help to create a shared agreement about the solutions. In fact, it is important that the team is commitment on …
Today, more than ever, organizations need to build products that add higher value to customers and the business. To be more competitive companies need to develop products in a faster way by reducing costs. To accomplish this goal organizations can use the Nexus framework to scale software and product development. …
Scrum framework focuses totally on how the end user will interact with the software. Use cases help to describe how an end user utilizes the system. What is a Use Case? A use case represents a description of the ways an end-user wants to utilize a system. They capture the …
Today technology moves at light speed. Let’s see how to keep up with technology with Scrum. The waterfall method In the past, the standard way to manage software development was by using the “waterfall method”, basically the process was to execute activities sequentially. In fact, in waterfall, the development starts …
Scrum relies on transparency. It is important to notice that transparency does not occur overnight, but is a path. The importance of transparency Transparency makes visible the progress of work and team. As a result, when the team achieves its goal, people who are responsible for it can be identified …
Scrum does not clearly define any controls. As Scrum is a risk-reduction framework it already contains various risk controls. In fact it is important to remember that Scrum aims at solving complicated issues to reach project success. Here is a list of controls that can reduce the risk of project …
The Scrum Team is a self-organized team that constantly looks to improve its way of working. What is the Sprint Restrospective? The Sprint Retrospective is the final event of the Sprint. In fact, it occurs after the Sprint Review and prior to the next Sprint Planning. It represents the moment …
What is the Sprint Review? The Sprint Review is an informal meeting held at the end of the Sprint. This meeting lasts four hours for one month Sprints. For shorter Sprints, the event is usually shorter. During this meeting the Scrum team shows to the Product Owner and the stakeholders …
An artifact is something that we create. In general, it can be a handmade object, or a result of human activity. For instance, a design, a document, or more in general a project deliverable. Scrum has three main artifacts: the Product Backlog, the Sprint Backlog, and the Product Increment. The …
In Scrum, development teams have the objective to reach Sprint goals. Impediments can jeopardize the achievement of the Sprint‘s objectives. What is an impediment? In Scrum, an impediment refers to anything that holds a development team back from being productive. Basically, it is any problem that blocks the team from …
One of the five Scrum events The Daily Scrum is one of the Scrum events. During this meeting the team members synchronize their progress with each other. They create a plan for the next 24 hours. The Daily Scrum is held every day of the Sprint and lasts at most …
The team decides about the work In Scrum, after the Sprint Planning, the Development Team starts to work on the Sprint Backlog items. In fact, each member of the team analyzes the items in the Sprint Backlog. Afterwards, the team decides who will work on what tasks. Even if team …
Increase the level of transparency The Sprint Backlog increases the transparency of information about what is the work planned and accomplished for the next Sprint by the Development Team. In fact, the Sprint Backlog is a highly visible, it represents a snapshot of the work that the Development Team plans …
Scrum already drives most of the world’s top technology companies. Now it’s starting to spread to every domain where leaders wrestle with complex projects. There is no more lucid explainer of Scrum and its bright promise than Jeff Sutherland, the man who put together the first Scrum team more than …
Sprint planning is one of the events of the Scrum Framework. This event kicks off the Sprint. It can last a maximum of eight hours for a one-month Sprint. For shorter Sprints, the event can be shorter. The purpose of this meeting is to determine the Sprint plan and set …
Scrum is a lightweight framework which helps organizations to develop and sustain complex products. The Scrum framework has: Roles: Scrum Master, Product Owner, Development Team Artifacts: Product Backlog, Sprint Backlog, Increment Events: Sprint, Sprint Planning, Daily Scrum, Sprint Review and Retrospective Scrum addresses complexity by making information transparent. So that, …
In Scrum, the definition of what is to be built is created during Sprint planning. Sprint Planning answers the following: What can be delivered in the Increment resulting from the upcoming Sprint? How will the work needed to deliver the Increment be achieved? Sprint planning produces a Sprint Backlog, a …
Scrum states that the scope of a Sprint cannot be changed once the Sprint begins. So, all requirements related to the Sprint are frozen until it ends. If an important change request – that may have a significant impact on a Sprint in progress – arises the Product Owner talk …
In Scrum, a Sprint can be considered like a project with a duration that is at most one month. In fact, Sprints, like projects, have goals to be accomplished. The Sprint begins with Planning and ends with Review and Retrospective. Each day of the Sprint is marked by a brief …
Organizations who want to adopt Scrum should have guidelines about how to structure the Development Team. The Scrum Master coaches the employees about Scrum and empirical product development and the organization about Scrum values and principles. He/She collaborates with other Scrum Master for organization-wide Scrum adoption. The organization should also …
It contains only those items to complete during each Sprint. The Sprint Backlog is a forecast by the Development Team about what functionality will be in the next Increment. In addition, the Sprint Backlog contains the work needed to deliver that functionality into a “Done” Increment. Nobody can change the …
The Development Team manages how the development work is planned, performed and controlled. Whereas, the people aspects of the Scrum Team like hiring, firing, compensation and other aspects are handled by HR authority in the organization. It is only the Development Team that decides how to get the development work …
In Scrum, a development team performs the work of delivering a potentially releasable increment of “done” product at the end of each sprint. The best size of the development team is small enough to remain fast and large enough to complete significant work within a sprint. Scrum recommends from 3 …
The Scrum Product Owner is the Voice of the Customer. The ideal Product Owner is the person paying for the product and generally speaking it is a business-facing person. It is important that he/she understands the market, product, business and any constraints involved. The role requires strong inclination towards a …
The Product Owner maximizes the value of the product by constantly collaborating with stakeholders. He/She is responsible for maintaining the product backlog order by sequencing the items to best achieve company goals. Product backlog items are constantly updated by the Product Owner who looks for the latest insights and market …
A Scrum Master is a coach at organization level. A Scrum Master is a coach who coaches the development team in executing Agile practices to complete the work the Product Owner prioritizes. He/She coaches the Development Team to create high-value products. In addition, he/she coaches the Product Owner about managing …
The Scrum Master ensures that the Scrum Team adheres to the Scrum rules, practices and values. The Scrum Master serves the team by helping it to become self-organized and make daily decisions by itself. Moreover, when a company starts adopting Scrum, the team can get a lot of external interruptions. …
Scrum is a risk reduction framework for building complex products. Scrum mitigates the risks associated to the traditional project management approach by distributing the responsibilities of the Project Manager role among the three Scrum roles. In addition, it is important to remember that the Product Owner and the Scrum Master …
In Scrum, there can be more than one team working on the same product. Multiple Scrum Teams that work together on the same product use only one Product Backlog. Each Product Backlog item is estimated by the Development Team during Sprint Planning and through a continuous process called Product Backlog …
In Scrum, definition of “Done” is useful to provide clarity on the required work standard. The definition of “Done” is defined by the Development Team and it does not have to be approved by Product Owner. It contains information that can be used by teams to select items during Sprint …
In Scrum, the Product Backlog contains the product features that have to be developed. Product Backlog is constantly refined by the Product Owner and Development Team. The activity usually consumes no more than 10% of the capacity of the Development Team. The objective is to identify what the product needs …
In traditional project management, beyond quality, communication etc, Project Manager manages scope, cost, quality and schedule. In Scrum, the Product Owner manages the scope through the Product Backlog. The Product Owner manages the cost of product features by putting them together in order to maximize the value produced by the …
In traditional project management, when a new project starts the Project Manager creates plans based on predicted work. Then, he/she monitors and controls these plans till the end of the project. This is also true for the staffing plan: the Project Manager creates the plan and then monitors the utilization …
Scrum is not a process or methodology, it is a framework that allows the delivery of products of the highest possible value. It has a structure that enables a simple but effective way of working together towards a focused goal. A team within an industry sector can choose to use …
In Scrum the team respects the fact that the future cannot be predicted. Empiricism helps people to face uncertain and complex problems. It is also important to obtain clarity and refine the product. In fact, each iteration is an opportunity to solve a problem and gain more clarity. Keep in …
In product development, it is very common to have product features batched together and delivered to production in one or two big limited releases. By acting this way companies treat all product features as having the same value with no consideration for time. Scrum has a business role that is …
English
Arabic
Chinese (Simplified)
Dutch
French
German
Italian
Portuguese
Russian
Spanish