Book Image

Manage Your SAP Projects with SAP Activate

By : Vinay Singh
Book Image

Manage Your SAP Projects with SAP Activate

By: Vinay Singh

Overview of this book

It has been a general observation that most SAP consultants and professionals are used to the conventional waterfall methodology. Traditionally, this method has been there for ages and we all grew up learning about it and started practicing it in real world. The evolution of agile methodology has revolutionized the way we manage our projects and businesses. SAP Activate is an innovative, next generation business suite that allows producing working deliverables straight away. Manage your SAP Project with SAP Activate, will take your learning to the next level. The book promises to make you understand and practice the SAP Activate Framework. The focus is to take you on a journey of all the phases of SAP Activate methodology and make you understand all the phases with real time project examples. The author explains how SAP Activate methodology can be used through real-world use cases, with a comprehensive discussion on Agile and Scrum, in the context of SAP Project. You will get familiar with SAP S4HANA which is an incredibly innovative platform for businesses which can store business data, interpret it, analyze it, process it in real time, and use it when it's needed depending upon the business requirement.
Table of Contents (6 chapters)

Creating a product backlog


As discussed in Chapter 4, Understanding Agile and Scrum, the product backlog is a list of user stories (requirements) for implementing a product vision. It is a dynamic prioritized requirements list; the details vary by the priority of the requirement (the requirement list gets detailed as the team gets closer to implementing them). The product owner is responsible for it.

Since the product backlog is one of the most important components, it's very important to also know what it is not. The product backlog is not:

  • A requirement specification with loads of details
  • A list of activities of how to transform requirement into product
  • A design documentation

The product backlog provides various levels of detail; the level of details depends on the position of an entry within the scrum product backlog. They are as follows:

  • User story: A description of the desired functionality told from the perspective of a user or customer. A user story is a very easy yet powerful tool to bring...