Process Vs. Agility. Why Not Have Both? Brought to you by

Transcription

1 Process Vs. Agility Why Not Have Both? Brought to you by

2 Hi everyone! CEO and Co-founder of Navvia Architect of the Navvia Process Designer Overall responsibility for product development, marketing and services 35 years of IT experience with progressively senior technical and managerial roles David Mainville

3 PROCESS Vs. Agility

4 What do you think when you hear PROCESS Agility

5 What do you think when you hear PROCESS Agility Rigid Bureaucratic Stodgy Inflexible Slow Frustrating Flexible Fast Nimble Adaptable Quick Satisfying

6 A dichotomy? There are no absolutes it is a continuum

7 Good processes deliver results How long does it take you to withdraw $100 from an ATM?

8 Ignoring process will hurt agility What happens if you fail to follow the process of warming up before a run?

9 PROCESS underpins Agility Driving Business Outcomes There is no Agility without process

10 A tale of two apps Presentation App Collaboration App Both continuously delivering new functionality

11 Very different outcomes Presentation UI seems to change at random Previous working functionality breaks Different behavior across platforms Poor support / help Zero advance warning or communication Collaboration Plenty of advanced communication Excellent reliability No surprises Built-in notifications, walkthroughs and help Excellent customer feedback program

12 Lessons learned Questions I would ask the team What drove the changes? The app used to work great, lots of change with little improvement to functionality Why is the application so unstable? Was there a focus on functionality and speed over quality? Was user experience considered? The app worked differently from day to day What are the broader ramifications of all this disruption? We openly complained to anyone who would listen Presentation App

13 Audience participation Does your organization embrace an Agile Development Methodology? Yes, spanning business, development, operations and clients Yes, but only in the development organization No, we are actively considering it No, too much organizational change required What s Agile?

14 The IT view of Agility is often limited There is a focus on the Dev organization: Develop Build Package / source control Testing Deployment

15 Agility is bigger than the Dev team Source: DevOps Reference Architecture, Source: IBM

16 Agile development principles Customer satisfaction by early and continuous delivery of valuable software Welcome changing requirements, even in late development Working software is delivered frequently (weeks rather than months) Close, daily cooperation between business people and developers Projects are built around motivated individuals, who should be trusted Face-to-face conversation is the best form of communication (co-location) Working software is the principal measure of progress Sustainable development, able to maintain a constant pace Continuous attention to technical excellence and good design Simplicity the art of maximizing the amount of work not done is essential Self-organizing teams Regular adaptation to changing circumstance Source: Agile Manifesto -

17 Agility is underpinned by process and delivered by people supported with tools

18 Agility is underpinned by process How do we define and document the business requirements and outcomes? How do teams collaborate and what tools support collaboration? What are the processes and tools to define and manage work? What processes and tools do we need to manage source code? How do we automate the build, testing and deployment of code? How do we ensure things are working in production? What processes are in place to listen to the voice of the customer?

19 There are a lot of misconceptions / myths It is a skill, position or department It s all about automation It s about x deployments a day It s about learning a new language It clashes with processes / ITIL It s only for modern tools It s new It s easy / a silver bullet There is an instant benefit It means NO requirements, architecture or documentation It only relates to development Big bang is best all or nothing It means no planning just do it Source: Smit Patel Peter Measeyhttp://

20 And a lot of hype DevOps is currently at the peak of the Gartner Hype cycle Source: Hype Cycle for Application Development, July Gartner

21 Takeaways Process is essential to agility Process encompass your entire organization and includes your clients You can t automate (build, testing, deployment ) without first understanding the process Processes are the nervous system driving the agile organization

22 PROCESS underpins Agility Driving Business Outcomes There is no Agility without process

23 An Agile approach to process design DEMO

24 Process Designer Register for a navvia.com/demo