I have been working on different kind of software projects implementation using the water fall methodology. now some of my clients want to shift to agile methodology. what do I need to take into consideration for such a change and what steps needed to start follow up with the new methodology though some client will remain working with using the waterfall way but some clients are insisting on the agile way. Saving Changes...
I would start by working with your clients to understand what *they* mean by agile. Agile is a set of guiding principles rather than a methodology. Some people use the term interchangeably with Scrum, or other specific, well defined solution approaches. Others are more focused on principles of business agility such as value delivery over extensive documentation and managing change in environments with high uncertainty. When your clients insist on agile, what is that in their minds in terms of both execution and expected benefits?
I integrate agile approaches into large long-term projects all the time and frequently I don't even use the word agile. Some team members have very negative experiences after working in "agile" environments more focused on following a fixed set of rules called Agile than approaches rationally tailored to the relavent business context.
...
1 reply by Nour Atwy
Feb 14, 2023 3:58 AM
Nour Atwy
...
Thank you Kieth for your reply. i understand that waterfall is a kind of project lifecycle whereas agile refers to a more general approach to organization and productivity using techniques which emphasize practices like iterative, incremental and continuous delivery, self-organizing teams, customer collaboration and responding to change. I think the agile frameworks are more likely for software development because the delivery is the key. but in my situation i work on implementation of enterprise financial solutions that already developed and it require configuration, parameterization and some additional customizations to satisfy the client business need. the difficulty here is that, this kind of project used to be planned in the following way a business requirement workshop, implement the requirement , UAT acceptance ,then go live. but how to apply that to agile method. how to know that it's the time to go live with the project.
Saving Changes...
Thomas WalentaGlobal Project Economy ExpertHackenheim, Germany
Nour,
given that you are in the SW industry and your market seems to demand agile, whatever that means to them, often just Scrum, just get knowledge about agile concepts, read a lot but - do not forget that project management is getting things done, regardless how.
the first thing to understand is agile is not a methodology. Merely copying a set of practices, ceremonies and roles won't result in better outcomes for your team or your stakeholders.
I'd echo Keith's advice to confirm with the clients on what they mean by agile and why they are pushing for it...
Senior Projects Manager | Field & Marten AssociatesNew Westminster, British Columbia, Canada
Nour
My thoughts are in line with Keith and Kiron. It is important to understand that Agile is a mindset before anything, and not a methodology. You need to be Agile in order to do Agile and this is a culture you have to build within the whOle organziation top to bottom.
I would start by working with your clients to understand what *they* mean by agile. Agile is a set of guiding principles rather than a methodology. Some people use the term interchangeably with Scrum, or other specific, well defined solution approaches. Others are more focused on principles of business agility such as value delivery over extensive documentation and managing change in environments with high uncertainty. When your clients insist on agile, what is that in their minds in terms of both execution and expected benefits?
I integrate agile approaches into large long-term projects all the time and frequently I don't even use the word agile. Some team members have very negative experiences after working in "agile" environments more focused on following a fixed set of rules called Agile than approaches rationally tailored to the relavent business context.
Thank you Kieth for your reply. i understand that waterfall is a kind of project lifecycle whereas agile refers to a more general approach to organization and productivity using techniques which emphasize practices like iterative, incremental and continuous delivery, self-organizing teams, customer collaboration and responding to change. I think the agile frameworks are more likely for software development because the delivery is the key. but in my situation i work on implementation of enterprise financial solutions that already developed and it require configuration, parameterization and some additional customizations to satisfy the client business need. the difficulty here is that, this kind of project used to be planned in the following way a business requirement workshop, implement the requirement , UAT acceptance ,then go live. but how to apply that to agile method. how to know that it's the time to go live with the project.
...
1 reply by Keith Novak
Feb 15, 2023 12:28 PM
Keith Novak
...
I work in the design and manufacture of commercial airplanes. Not only is it heavily regulated like finance, but we also have the additional constraints of extremely deep supply chains, and the physics involved in manufacturing processes. The configuration management requirements of extremely complex safely critical products with a 30+ year nominal lifespan are actually quite extensive.
"It's really complex so we can't employ business agility." is (respectfully) quite frankly an excuse. There is actually a lot of latitude between the control points in highly regulated industries where must show compliance to regulations.
Finance like law, deals in paperwork related to to physical entities that provide the underlying value. Even in the legal industry where the financial regulations themselves are codified, there is a lot of activity going on between the formal court filings where creative delivery processes may be utilized. It is re-imagining how you can employ business agility while maintaining compliance that is the true challenge.
Saving Changes...
Sergio Luis ConteHelping to create solutions for everyone| Worldwide based OrganizationsBuenos Aires, Argentina
First thing to do is to understand that waterfall is a like cycle and agile is an approach that can be used with any life cycle including waterfall. Second, is to understand what agile is. If you are talking about creating software products then the Manifiesto for Agile Software Development is the checklist to use BUT do not forget reading "About the Manifesto" inside the website. The key thing is do not forget that agile is an approach then it will impact the organization as a whole because it is based on systemic theory where organizations are considered open and adaptable systems. A good point to start is DAD but my recommendation is going to what Scott and Mark did in the begining with DA. Other way to have a big picture is taking a look to SAFe. I am not saying that you use SAFe just you can take a big picture about how value streams are impacted. In this case, a good reference is all the work created by Al Shaloway.
...
1 reply by Kevin Bast
Mar 31, 2023 12:19 PM
Kevin Bast
...
Hi Sergio - can you elaborate on how you see how Agile can apply a waterfall lifecycle? What's your view or perspective on how you can incorporate the two - or are you considering it "hybrid"? Thanks for your input.
Your organization's request to transition to Agile is on a high level.
To make the first step, it is necessary to start by clarifying:
1. The reason your organization needs to transition to Agile;
2. What your organization is expecting when transitioning to Agile, what problems are you currently facing with the Waterfall model and will those be resolved with an Agile approach;
3. What metrics will be used to measure success (Definition of Done - DoD), are all members of the organization aware of their roles;
4. How much do the members of your organization understand about Agile, what is the training plan and implementation strategy;
5. Establish the timeline for transition, what potential risks and projects will be affected, and what is the level of risk acceptance? The transition to Agile cannot be done by a single individual, it takes a team to make it happen, so get everyone involved in your “Agile project” to make it work. Saving Changes...
I agree with Sergio. You must start with Disciplined Agile, which gives guidance to make decisions about agile solutions, iterative and incremental. Saving Changes...
Thank you Kieth for your reply. i understand that waterfall is a kind of project lifecycle whereas agile refers to a more general approach to organization and productivity using techniques which emphasize practices like iterative, incremental and continuous delivery, self-organizing teams, customer collaboration and responding to change. I think the agile frameworks are more likely for software development because the delivery is the key. but in my situation i work on implementation of enterprise financial solutions that already developed and it require configuration, parameterization and some additional customizations to satisfy the client business need. the difficulty here is that, this kind of project used to be planned in the following way a business requirement workshop, implement the requirement , UAT acceptance ,then go live. but how to apply that to agile method. how to know that it's the time to go live with the project.
I work in the design and manufacture of commercial airplanes. Not only is it heavily regulated like finance, but we also have the additional constraints of extremely deep supply chains, and the physics involved in manufacturing processes. The configuration management requirements of extremely complex safely critical products with a 30+ year nominal lifespan are actually quite extensive.
"It's really complex so we can't employ business agility." is (respectfully) quite frankly an excuse. There is actually a lot of latitude between the control points in highly regulated industries where must show compliance to regulations.
Finance like law, deals in paperwork related to to physical entities that provide the underlying value. Even in the legal industry where the financial regulations themselves are codified, there is a lot of activity going on between the formal court filings where creative delivery processes may be utilized. It is re-imagining how you can employ business agility while maintaining compliance that is the true challenge. Saving Changes...
Community Champion
