EnterpriseAgility

also can you share how a collaborative architecture supports Enterprise Agility?

collaborative architecture is essentially a framework to share assets

@kartik_next those assets could be code, documents, ideas etc. .. it also provides a framework to organize these assets in a way that makes it easy to consume and share

transparency and collaboration are central to enteprise agility - but when scaling it broadly there is a need to do this in an organized way to minimize noise and maximize actual re-use..

scaling it out before getting it right in smaller settings first.

also some organizations lose sight of enterprise agility in the zeal to roll out agile scrum practices and the process becomes the goal..

Optimization around individual projects. i.e., workgroups doing work in isolation, meeting their business requirements, and then moving on to the next thing... at the expense of a central enterprise view and governance

There's a simple recipe. Centralize tools/teams and plug in, organize the projects around biz/tech objectives, create repeatable dev-deploy processes, measure metrics along the way,& improve

How do you enable “process reuse”?

When did you guys realize there was a big opportunity in #devops and infrastructure as code? What was the spark for ColabNet?

From an #ALM tool perspective, openness is important, but consistency of artifact nomenclature and workflows is mandatory. Otherwise, it's impossible to share processes and downstream project software application IP - rq'd for enterprise agility

@HalieNoble By "process reuse" I mean codifying agile planning through deployment toolchains into a library, then instantly provisioned (using our product TeamForge) to onboard new teams. Improvements also be pushed to those provisioned projects.

@billportelli - simply said, if one project figures out how to develop 10% faster, then those improvements can be shared as well

@HalieNoble I interview people all the time and the top answer there is use best practices and community guidelines there are tons of resources

On the business side get a good lawyer :-)

I'd say tool usage transparency and consistent usage practices are key for opensource tools to be adopted well in the enterprise

worst thing is to have unregulated sprawl of opensource tools. that can be hard and expensive to corral later.

Business model is straightforward. Annual subscription based licenses for an integrated set of ALM and collaboration tools that we sell to the enterprise. We've hosted (since 1999) in our data center or deploy on the clients site.

@BillPortelli is that all SaaS?

Main problem we solve is helping companies gain visibility and governance of their globally distributed IP assets / teams. This is enabled by a collaborative approach to accelerate development, innovation and driving down development / deployment costs.

Said in simple terms, we help enterprises organize their IT, then scale to leverage their best people and software assets to gain competitive advantage through developing great software

@BillPortelli your url is awesome collab.net did you get that or buy it?

I'd like to take the credit but it was Brian Behlendorf who originally came up with the name for the company and the URL in 1999. The name has never been more appropriate- collaborative software development over the internet

Our most advanced customers are getting 40-50% time to market reduction, service level quality improvement, app rationalization, and 10s of millions of annual savings. Not buzzwords... it's a reality with the right approach.

many companies starting off with devops are begining with automating their continuous deployment processes in the dev/test cycle first.

Our customers demand openness from a development process, tool and target platform perspective. Also need to set approaches for deploying to infrastructure inside and outside the org.

Where does the initial #DevOps conversation typically start in a large organization that is not traditionally in the software development industry?

#DevOps requires Dev and Ops teams to talk and engage- an enterprise grade collaboration platform to drive visibility and improvement is mandatory.

@BillPortelli @kartik_next do you see this operationalized in your customer environments?

@HalieNoble In my experience the #DevOps conversation typically starts as a quality of service discussion

absolutely. most of our customers have adopted devops practices to some extent.. typically starts in the dev cycle before extending downstream

@kartik_next how does security get into that discusion or is it there from beginning

security considerations become more relevant as devops practices get closer to production, especially in governed enteprises

i believe agile at scale requires more rigor..

; Embrace the favorite #ALM tools and agile/hybrid processes of the workgroup. Then codify the "right set" to get repeatability of process across workgroups. Measure and improve

a good collaboration platform thats open yet secure is key. The other key factor is consistency of methodology , tools and such.

@kartik_next Rigor in what? In leadership, commitment to value, structure?

@HalieNoble agile is a rigorous process from a methodology perspective and requires commitment to value and structure

Execs I talk to are concerned about agile sprawl, lack of consistent tools and processes, and loss of visibility. Hard to #scale #agile to the enterprise unless these issues are tackled head on.

Bill I work in the social enterprise space and it's always I want mobile first but the web agile is easier to use than mobile. The mindset is critical

@HalieNoble and it important to follow best practices and get the practice right before starting to evolve or change it to meet specific circumstances

#Forrester states only 32% of teams have mastered agile planning & 20% have scaled to the enterprise. But only 1 in 7 projects have connected agile planning to ALM. DevOps requires all teams to link planning and ALM in a consistent fashion

at the workgroup level its starting to make an impact but agile adoption at scale is still work in progress

I get this question all the time "can agile work in mobile first" dev cycle

do you think that is how agile must enter an enterprise? Trickling from small groups until it spreads organization wide?

@mikeonsing certainly.. in some ways its easier to adopt agile in for newer initiatives and forming teams

; I agree with Kartik. Industry has conquered agile at the workgroup. The trick is creating and scaling an integrated approach containing both agile/mixed processes and an ALMplatform. Difficult without a managed approach.

@HalieNoble I think organizations should broadly commit to agile but its better to get a new methodology like agile right before scaling it broadly

What do you think of the Github for Enterprise does that help agile?

I saw that at AWS re:invent where their SaaS product is not available for enterprises that is the trend that agile is in the enterprise as first class citizen; validates the mega trend

@HalieNoble It's important not to confuse #agile development with enterprise agility. They are different. One is about workgroup development processes. The latter is about sharing of processes, enterprise architecture, and software IP

@mikeonsing I think github is still maturing but the new collaboration and access control features are steps in the right direction