I'm trying to define wich is the best trade off to release a service "reliable" in a people organization where the service development is managed with an approch agile but service implementation is fulfilled in a waterfall way. Have you any sugestion? Saving Changes...
Reliable is just one subset of quality requirements. Whether you take a predictive or adaptive approach to delivering the service, quality practices need to be used to ensure that all such requirements are met.
Kiron
...
1 reply by Santi Messina
Feb 05, 2021 9:57 AM
Santi Messina
...
Thank you Kiron!
What you write is the key I am looking for.
Often those involved in operational activities cannot manage a predictive or adaptive approach as required in an agile organization.
Wich is the best way to pass the requirements from agile to waterfall organizations to have a minimum impact on reliability?
Reliable is just one subset of quality requirements. Whether you take a predictive or adaptive approach to delivering the service, quality practices need to be used to ensure that all such requirements are met.
Kiron
Thank you Kiron!
What you write is the key I am looking for.
Often those involved in operational activities cannot manage a predictive or adaptive approach as required in an agile organization.
Wich is the best way to pass the requirements from agile to waterfall organizations to have a minimum impact on reliability? Saving Changes...
Reliability is less a concern than meeting overall requirements. When it comes to requirements handover in hybrid situations, it is important to pick a requirements modeling technique which works for both the agile and waterfall teams rather than what is best for just one.
Kiron Saving Changes...
Thomas WalentaGlobal Project Economy ExpertHackenheim, Germany
Santi
do not understand what you mean service implementation is managed in a waterfall way. Is that implementation meaning that you provide the service? If so, it probably is rather operations than a project, and the life cycle would not be a project lifecycle, but a product (service) life cycle. This is not often called waterfall, as it is not a project (it is unlimited in time per se).
I could imaging that the 'reliable' criterium is measured and continually improved. Frameworks like ITIL help with setting this up (and provide lifecycles). I would expect that a development project for this service (agile or not) also delivers such a framework for operating the services.
Then, maybe another aspect, an agile mindset, as appropriate for an agile project, may or may not be appropriate for service delivery. My experience tells me that they should be different. A service delivery has different customers and success criteria and funding requirements and governance as a project. Saving Changes...
Reliability is getting the same result with limited variability, even if it is the wrong result.
If you are trying to ensure reliability using an agile development model, then I would suggest integrating a Six Sigma approach. At each introduction of new functionality, sufficient tests are performed prior to implementation to ensure that the functionality operates consistently while taking into account your various possible error sources.
The larger waterfall plan needs to take into account that the functionality is being added in each new release, that all the planned functionality is included in the release plan, and that each new iteration does not affect the reliability/variation of the previously released functionality.
If the functions of the service work together to serve some larger objective, then the reliability testing needs to consider a bottom to top approach of component reliability up through the complete service offering. Saving Changes...
Sergio Luis ConteHelping to create solutions for everyone| Worldwide based OrganizationsBuenos Aires, Argentina
Waterfall is a life cycle. Agile is an approach. You can use Agile with waterfall life cycle. In fact, just in case you are creating software product, read the Manifesto for Agile Software Development and you will not find a line about to use an interactive or incremental or interactive-incremental life cycle. No matter that, myself and others use Agile with waterfall life cycle from years ago. So, the important thing is to stay clear about what Agile is then put it on practice using the life cycle that best fits to create the solution (a service in this case). Saving Changes...
Thank You All!!!
Your comments made me think about on what the solutions can be in my specific case
I'll approach to define a requirements modelling as suggested by Kiron to define an interface between agile and waterfall teams Saving Changes...
