Agile Insider
Published in

Agile Insider

Why the big picture is important and how to keep it

There are many great tools, techniques and methodologies to collect requirements. You can use plain sentences, use cases, user stories or whatever what makes sense to you. One way or an other you will end up with a nice list in your pocket, where everything makes perfect sense, there are no gaps of contradictions of any kind. The first moment when my requirements start to transform from a set of sentences into the concept of a functioning software is magical. I hear the song of the angels, unicorns are dancing on rainbows and I feel fulfilled that I achieved something…




Exclusive and practical insights that enable the agile community to succeed.

Recommended from Medium

Using SANS SIFT Workstation or REMnux with SSL Decrypting Proxies

Add control to JSON Web Tokens generation on Laravel Passport

So Much Binary

dense tech stack world

ONT ID Framework Upgraded: Ontology’s Verifiable Credentials SDKs Now Open Source for All Go and…

Will HCL Places replace IBM Notes?

Send Email using MSFlow On Button Click from PowerApps

Custom Use Cases: Where You Need Big Objects

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store
A Product Owner with a pen

A Product Owner with a pen

As an IT Business Analyst and Product Owner I want to figure out how can we organize our work and life better.

More from Medium

How to develop your skills as a Product Owner or Product Manager to become a Product Leader

What are the characteristics of good user stories?

A picture of cog with “Best Practice” written on it.

11 Powerful questions to ask yourself as a Product Owner

What’s your Agile story?