A Long Time Ago…

As we develop the software , we will run into issues ... we add these issues to our 'to do list'...preferably to the current sprint (add to the sprint backlog). To see where everyone is, we will have informal meetings to tell each other what we are working on, what issues we have and what we will be working on next; in Scrum we call these meetings 'Daily Scrums' ... in SAFe, Daily Standup ( DSU). As we implement features, we will show how the working software increment look; in Scrum, we call this the Sprint Review Meeting... in SAFe,…

Together, with Diana (she, being the voice of the customer), we all create a prioritized 'feature list' -- in Scrum, we call this the Product Backlog. To actually implement something, we all meet and choose some features to implement first based on the priority of the features -- in Scrum we call this meeting a Sprint Planning Meeting... and the list of items to be implemented we call this the Sprint Backlog. To be continued...

Three decades ago, when I was a young programmer/analyst, I, together with two other programmers, worked closely with a person who represented the business. Let's call her Diana (not her real name). Diana lets us know what the business wants and what's important to them. She has a product in mind and all of us, together, we fleshed out the big idea into several functional chunks. To be continued...

A long time ago, software project development (and management) was simple, natural and common sense. Let me go back to those times... and tell you my story... the way software was developed and managed back then, from my experience and perspective. To be continued...