To learn more about Process Street and what we do check out our explainer video. For example, as a Process Street user, I need a wider range of HR checklists, so that I can better manage my HR workflows better. *User stories are a way of describing a feature set. This list evolves and changes priority with every sprint. Product backlog: Product owners create a prioritized list of features, known as user stories that could benefit the product.The team: Anyone else involved in building the product.Running the meetings and keeping things going. The scrum master: The leader, and protector of the team and the process.The product owner: The person responsible for defining the required product features The product owner thinks up the ideas that turn into products.Let’s go through each of these in more detail. Scrum relies on three key roles, three artifacts, and three ceremonies. Each independent project may run multiple sprints until all the features have been built. You continue the sprint until the project is feature complete. Scrum is an agile framework based on the sprint system, or “incremental releases”, which take from 1 to 3 weeks to complete. To jump to a specific section, click the appropriate link below:Īlternatively, to read the whole post – just keep on scrolling.

This post outlines the key takeaways from the team and takes a closer look at what Shape Up is as a whole. Our development team here at Process Street recently made the move from Scrum to Shape Up and I asked them how the two compare.

These are just a couple of examples of the differences between Shape Up and agile approaches such as Scrum.īut, what exactly is Shape Up? How does it, when put into practice, differ from Scrum? From sprints to cycles, and from product backlogs to …well…no backlog at all.

Shape up basecamp