Pivotal assumption – “An assumption on business case, priority, minimum viable offer, or requirement that if false will fundamentally change designs, deliverables, or timelines.” In my post on how organisational factors increase the bad impact of architectural debt, I referred to how the lack of clear business objectives and priorities slow you down and prevent […]
Archives for 2015
The Importance of the Backlog and the Product Owner
In a previous post, I wrote about the challenges and strains on roles and processes when a traditional waterfall (or even agile) organisation introduces devops. Most people focus on the tools needed and how you must establish a build pipeline and support for continuous deployment to production. However, the success of devops is in the […]
The Changing Development Organisation: The Software Architect
(intro to this post on devops) It has been a busy few months. Since my last post I have transitioned to a new role as part of day to day development (see linkedin.com/in/greger for more details) in the Collaboration Infrastructure Technology Group (UC, telephony, telepresence, conferencing, etc) in Cisco. Earlier, as part of Office of […]
A short comment on devops (and an intro…)
A few words about devops and as an introduction to my next post: Hosted services used to be developed and deployed very similar to how products are released (see figure). There was a development phase, then an integration and test phase, then the component would be released and installed, including going through one or more […]
RSS - Posts