We know that the Product Backlog is an order collection of the item (PBI) needed to improve the product. In other words, every PBI is a functional or non-functional requirement (or maybe a fix or other) that adds value to the product.


But what if the PBI asks to have a dedicated user area to share the document only for the paid users? Under these requirements, some architectural development is needed, maybe an authentication system.

The topic of this chapter is architecture.

The first thing to know is that the architecture emerges and evolves due to the requirements, like in the example before. So we don’t want an upfront analysis and development of the architecture in Scrum.

Another thing to know is that we want to add value in every sprint because Scrum is all about value. So we need to mix architectural development with the requirements in each sprint. So maybe at the start of the project, we can have like 40 story points in architecture and only 10 in functional/non-functional requirements because we start from zero, and during the project, we start to lower the point for the architecture.

For the exam you need to remember that:

  • The architecture emerges and evolves during each sprint;
  • We avoid upfront architecture analysis or development to avoid waste;
  • At the start of the projects, we need more architecture for starting the project, but we also need to release value with it.

References:

Share on: