This is my current work and thinking on how to do Scrum within heavily regulated industries like healthcare, government, and finance. For more information join my community at http://scrumandcompliance.com/
CollabNet was founded in 1999 with the goal of creating a better way to build software. At that time Brian Behlendorf’s strategy (our founder) was focused on “how to connect talented developers regardless of where everyone was physically located”. In today’s terminology, CollabNet wanted to enable “geographically distributed development teams” and provide them a way to all work as ONE TEAM. Finding that CVS, one of the most popular version control systems available at the time, had various issues, CollabNet decided to commission development of a brand new version control system called Subversion. In 2000, CollabNet founded the Subversion open source project and recruited its first developers.
Since then, we have continued to sponsor and foster the Subversion project. This includes: hosting the physical project servers in our data center, guaranteeing uptime, providing technical support, and working with the press and analyst community to increase exposure and drive adoption. Perhaps most importantly, we maintain a team of full-time Subversion committers who are dedicated to contributing code and driving a product roadmap. As most of you know, we recently announced version 1.7 that finally addressed Merge Tracking, this was a big request from the community.
For companies who have now standardized on Subversion and are then looking to have Technical Support (like having insurance for SVN – someone to call if there is major issue) we offer 3 levels of Support which you can find on our website. We also provide migrations services and web based training. From our openCollabNet site you can download our CollabNet Subversion that EXTENDS SVN giving you additional functionality like Certified binaries and IDE support.
Along with our dedication to Subversion we also provide the CollabNet TeamForge platform which will cover shortly.
I would argue that introducing compliance only complicates this issue.
“Scaling is the last thing you should do” – Bas Vodde, Craig Larman, Martin Fowler, Jeff Sutherland, Ken Schwaber
I would argue that introducing compliance only complicates this issue.
“Scaling is the last thing you should do” – Bas Vodde, Craig Larman, Martin Fowler, Jeff Sutherland, Ken Schwaber
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)
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”
Is the Open Source model of working good? Does it produce results?
Wikipedia?
Subversion
Elaborate our services and product offerings
Gmail was invented during 20% time
http://www.mas.gov.sg/index.html (Monetary Authority of Singapore)
Former solution was from a proven vendor in the industry and we knew it had audit proof controls, but by the time CollabNet came in, we realized that (former solution) was much less cost effective. CollabNet was three times more cost-effective. We did an actual ROI study with Forrester, and over a three-year period, CollabNet was one third the cost, including the rollout of all these applications and maintenance costs.
CollabNet was a much less complicated solution, was much more graceful to meet our needs, easier to administer, and easier for developers to train up and to use.
The solution also included collaboration capabilities.
The solution was more flexible.
Instead of a one-size-fits-all solution, we could, for more risk-averse platforms, have a thicker process with more controls; and for platforms that needed to be more agile, we could have a more agile process.