Agile Requirements@Scale: Achieving a balance between compliance /governance and agilityCherifa
schedule 6 months agoSold Out!
You can earn CDUs...
"We have reached an impasse because of our regulations and current governance and cannot accelerate our agile adoption” " Does this sound like a common issue? Government, large and product-centric enterprises in aerospace, and automotive, are striving for more agility in their solution delivery. However, those organizations are bound with heavy governance, are stuck on how to comply with their regulations and at the same time being agile. Compliance is generally perceived in the software community as a way to evaluate solution delivery process from a formal and document-based perspective and many argue that Compliance/Governance and AGILE are just not compatible. The motivation of this presentation is to dispel this myth.
Compliance is one of the scaling factor that makes agile practices more complex to adopt. However it is possible to find a balance. What is needed is a different approach, one that leverages agile and lean techniques to make Agile Requirements Definition and Management practices more scalable.
- -Should you capture requirements up front or iteratively throughout the project?
- Should you write detailed specifications as interpreted by some audit officers, light weight specifications, or something in between?
- Should you take a use-case driven approach, a user story driven approach, or something else?
Do agile requirements strategies really work? Do they scale? Come listen /meet with the speaker who have a long experiences around what really works in practice.
In this presentation, we will discuss strategies for the balancing act between governance and agile.