Project Management

Please login or join to subscribe to this thread

The True Agile Approach

linkedin twitter facebook   Agile   Disciplined Agile  
avatar
Abhijit Ghorpade Edison, Nj, United States
So what is Agile? Based on the industry experience that I have been exposed to so far, here's what I gathered on how different teams are trying to implement projects using Agile
1. A hybrid of waterfall and agile - but using the terminologies of Agile.
2. Using the prescribed rituals (stand-ups, Sprint planning, retro etc.) but just checking the box (for the sake of it)
3. An approach that is not product focussed but just focused on velocity and points - Instead of delivering a functional skateboard or a bicycle, the deliverable is a half baked car.
4. The basic required eco-system - a) Mature team b) Accessible product owner c) commitment to the scoped/planned points for the Sprint - Either all or some are missing - causing projects/products to fail.
Here's my simple approach on Agile where I was lucky enough to be a part of and what we were able to follow / achieve -
1. Architecture - ensures a good enough architecture has been thought through (so we don't pay for design gaps during Sprints) - so dedicate the first Sprint or 2 for just ensuring a solidified architecture and design.
2. Stories - Have smaller stories rather than a big one. This ensures delivery and tangibility to enable measurement of progress
3. Scope commitment - Ensure the scoped stories are committed and only exceptions can truly remove/add scope. It shouldn't be a practice every Sprint to remove/add scope.
4. Product focus - Ensure the incremental view of Product is clear enough. So the Sprints are planned and deliver incremental product as opposed to just story points. Have a functional approach (a basic feature is good enough and then build on top of it. Rather than trying to build the entire functionality horizontally and one gets to see a workable feature only after several Sprints - that makes it a mini-waterfall).
5. Reachable product owner - as needed for quick reviews/feedback and clarifications. These little touch-points bring a lot of value to the product.
6. Team - The team is a bit courageous - Meaning - they voice over concerns if any. No idealism is assumed. Informal touch-points amongst team members is encouraged.
Rest - ceremonies and rituals are very well known - But just ensure the true value each Sprint brings to the table - that's the true measure!
Sort By:
< 1 2 >
avatar
Karl Vroman Owner| Vroman Consulting BV Reet, Van, Belgium
Dec 25, 2022 7:00 AM
Replying to Sergio Luis Conte
...
If you like to know what agile is my recommendation is going to the basement searching for the papers created into the place where everything started: USA DoD/NSF Agility Forum in the Raleigh University in 1990. Agile was born in manufacturing field, not in software field. Time after the concept was taken by software. Agile was born as an alternative of Lean. Lean and Agile are different things in the essence. And Agile, like Lean, is not about a life cycle or method, is an approach, a way of thinking and behave based on deliver value to customers and quality. Because is an approach is based on systemic theory then is a matter of architecture.
Hi Sergio,
I'm discovering agile to apply in high value assets projects, but keep hitting the 'this is in fact for software development' wall. Could you give guidance in where to look for more information or user stories for the Agile approach in these kinds of projects? Thank you, BR, Karl
...
1 reply by Sergio Luis Conte
Dec 04, 2023 5:05 AM
Sergio Luis Conte
...
Hi Karl. As I mentioned before Agile is an approach that was created in 1991 as an alternative to Lean. That´s because Agile and Lean are not the same. Agile was created in manufacturing. Time after the word Agile was taken by a group of people that have software development methods then that people wrote the famous Manifesto, but if you see it the word "software" is the name for a reason. Agile can be used with any life cycle (with waterfall for example). I am using agile with non-software projects from 1995 up to date. Where you can find information about agile in non-software projects? I am not able to redirect you to a place, to be honest.
avatar
Sergio Luis Conte Helping to create solutions for everyone| Worldwide based Organizations Buenos Aires, Argentina
Dec 03, 2023 9:42 AM
Replying to Karl Vroman
...
Hi Sergio,
I'm discovering agile to apply in high value assets projects, but keep hitting the 'this is in fact for software development' wall. Could you give guidance in where to look for more information or user stories for the Agile approach in these kinds of projects? Thank you, BR, Karl
Hi Karl. As I mentioned before Agile is an approach that was created in 1991 as an alternative to Lean. That´s because Agile and Lean are not the same. Agile was created in manufacturing. Time after the word Agile was taken by a group of people that have software development methods then that people wrote the famous Manifesto, but if you see it the word "software" is the name for a reason. Agile can be used with any life cycle (with waterfall for example). I am using agile with non-software projects from 1995 up to date. Where you can find information about agile in non-software projects? I am not able to redirect you to a place, to be honest.
< 1 2 >

Please login or join to reply

Content ID:
ADVERTISEMENTS

"The scientific theory I like best is that the rings of Saturn are composed entirely of lost airline luggage."

- Mark Russell

ADVERTISEMENT

Sponsors