Sprint Review Meeting

In Scrum, each Sprint should result in a potentially releasable Done product Increment. It doesn't seem like gathering requirements, procuring vendors, or defining processes alone will produce a potentially releasable Done product Increment. There's some level of up-front work to get ready for your first Sprint to have a vision and a sufficient Product Backlog for the team to refine and work on. However, it seems like the organization is still stuck in a sequential way of looking at product development. Instead of gathering requirements, start trying to build those requirements out, and get feedback to make sure that you understand the problem and the direction you are building out the solution.

This is even more fundamental than Scrum. Agility is about delivering value rapidly. Requirements, vendors, and processes don't add value. The product or service that the stakeholders want delivers value. What is the fastest way to get that product or service into the hands of stakeholders so they can see it and interact with it?

How do they share the story of the progress of the sprint and the value that was achieved? 

Are you sure you are sprinting at all? What transparency have you established over the meaning of a "Sprint", and that something of value must be delivered every time from the first Sprint onwards? Progress ought to be empirically demonstrated by the incremental release of finished work.

Only a potentially releasable product or working software will add value each sprint.

You seems to be still following a waterfall approach of building products. I would suggest to focus on features to be built in sprints rather than discussing the whole product in terms of requirement gathering and documenting. Requirements changes based on the feedback of every increment, so waterfall model proves to be costly for teams and companies most of the times.

• My Organization is transitioning from Waterfall to Agile and we are working on a new product . Right now we are still gathering the Functional and Non-Functional requirements, Procuring vendors , defining processes etc. Our Stakeholders complain they do not find value in our Sprint Review meetings.

• How do they share the story of the progress of the sprint and the value that was achieved? 

[1] It is better to do the ground work and preparatory work before starting the sprint.

[2] The activities listed are better to start and complete most of the items before starting the sprint.

[3] Every sprint need to deliver a Minimum Viable Product (MVP) and it should be releasable.

The "Product Owner" and stakeholders will review during the "Sprint Review".

The "Product Owner" will decide it can be release to production or not.

Thanks.