Before we started, Dan asked me, what's the point here. It's good / great to review that - here's why we are here.
The intersection is workflow management. Often multiple regulations at play just with one team or division. When you scale that the problem grows exponentially. [laz to show one team, then then, then 250)
Developers need to do their work. GRC often tells us how to work and it's never optional - it's required that's why its a regulation.
We need to respect both and find a happy medium. I think I've found a way.
We'll talk through some examples
More often than not Dev's are interested in their work product.
Auditors are interested in the documentation around that work product. This type of relationship isnt unique (You and your CPA)
Laz to tell his APAC story.
Reid Hoffman story
Our Thesis
Discuss the History of when I started in 2004 looking for candidates for the AOC project. Only 40 resumes in Dice.com with the term Scrum
Agile isn't going anywhere. It's hot, and it's how your engineers want to work. Finland is always ahead of technical trends – not sure why. But when I visited their largest SI, a company called Tieto, back in 2010 there CIO simply called it the “modern way to work”
Discuss the mechanics of Scrum here
Jeff Sutherland Story
My boss calls this communism.
Many customers ask me for More efficiency – the LG CNS example
Opening Page exercise
Hiring staff @ Danube – make them read this book.
Gmail was invented during 20% time
Intrinsic motivation vs. sticks and carrots
Gmail was invented during 20% time
Why not try to build this type of success into the social fabric of your companies?
Is the Open Source model of working good? Does it produce results?
Wikipedia?
Subversion
Gmail was invented during 20% time
Intrinsic motivation vs. sticks and carrots