Agile Days of Future Past

As published on Scrum Alliance Link

My current journey begins in August 1970, when Dr. Winston W. Royce presented his views on "Managing the Development of Large Software Systems" at the proceedings of IEEE WESCON. This revolutionary paper introduced software engineers like me to the world of Waterfall (or, as I like to call it, "what-the-fall"). But we usually skipped the part in our textbooks where Dr. Royce himself stated that pure Waterfall software development would never work. Dr. Royce stated that in order to eliminate most of the development risks, five additional features must be added to the basic what-the-fall approach.

Nine women can't make a baby in One month

Have you ever pissed a project manager? Not the work not done kinds; the one where the blood boils and the body shivers; I'll kill you kinds. I have, a number of times; and I can successfully say that I've escaped death and had a drink later. If you're one of those sadists who wish to become a successful project manager someday, this is how you be one. Well, not by frustrating your current project manager, instead by understanding the theoretical aspects of project management. Now I know when I talk about theory many of you'll say that bookish knowledge doesn't apply in practice. To those many, I say, this post is for a few good project managers who practice the correct theoretical concepts. Authors who write books, write experience. In short I cannot convince you if you don't wish to be convinced. But if you have an open mind, this 10 minute post can improve your project management skills by 10 times.

3 Practices to execute constructive Sprint Reviews

One of the many frequent questions I usually get asked is - Why Agile? What are its benefits? Although, the answer to this question can lead to a never ending debate, I like to begin my answer with - Agile helps improve quality. How you ask? Let me explain. Software Quality reflects how well a deliverable complies with the functional and non-functional requirements. Agile teams shoulder the responsibility of maintaining this quality, but they aren't alone. Customer representatives and end-users collaborate with Agile teams to provide rapid feedback in order to correct any mistakes early in the project. This rapid feedback is one of the biggest reasons of improved quality on Agile projects and Sprint Review meeting is one Scrum ceremony where it can be extracted efficiently. The challenge is extracting it from the right individuals especially when they are introverts.