IndigoBlue's Second Wednesdays are monthly breakfast discussions between Senior Business and IT Stakeholders in complex organisations. By invitation only and limited to 10 guests, the discussions are open and candid.
Chatham House rules apply: no presentations, no publicity, no recordings, no vendors. Simply an engaging, informative discussion in a convivial atmosphere with excellent food.
Agile by its very nature is iterative and incremental aiming to produce high quality solutions that meet the evolving needs of the stakeholders. Whilst Technology departments in many organisations have undergone significant change in how they deliver projects, how much of the wider corporate enterprise has adapted and adopted new ways of working? Are we in danger of constraining potential success through a siloed implementation? What does Agile mean for the corporate planning cycle, for investment committees and post implementation reviews? How does the broader enterprise need to change in order to reflect the different approach and associated demands of Agile upon it?
Facilitator: Richard Piercy EVP Transformation & Digital Supply Chain at EMI
If you are interested in attending one of our Second Wednesday meetings or if you would like IndigoBlue to facilitate similar discussions within your organisation, please register your interest with Alban James:
Blog Post
Blog Post
2 Blog Posts
2 Blog Posts
2 Blog Posts
Blog Post2010 Topics (2010 Archive Page):
Blog Post
Blog PostFrom the Dot com boom to the quieter (but potentially deadlier) digital revolution, what's next for our IT leaders? The increasing ubiquity of technology in business combined with the commoditisation of IT services presents them with a challenge as business leaders can feel empowered to survive without an 'IT' function. This new sense of confidence (with a vengeance) is not without danger. The IT function needs to be reinvented at all levels to remain a guardian of corporate goals and values, as well as a visionary partner of the business. What will it look like and what role will the IT leaders of tomorrow fulfil?
Facilitator: Rob Smith
Uncertainties exist in all guises in complex programmes, and yet change needs to take place regardless. These uncertainties can range from sudden market upheavals through to technical challenges or functional unknowns. They are often viewed as risks, but removing them too early in the process can be equally dangerous. Predefining a new proposition before a market is fully understood can easily stifle speed to market, let alone create unnecessary cost. However, setting out on a business change without a clear understanding of the key uncertainties can ultimately lead to failure. This peer discussion will explore the art of optimising the removal of those uncertainties through incremental programme delivery.
Facilitator: Rob Smith
Few would argue against the pursuit of value in complex change programmes. However, pinning down a single, measurable notion for it, one that could give a practical compass across teams and peer groups, is tough. Is this common purpose even realistic or just wishful thinking? If not, doesn't forcing the issue come with possible downsides? Indeed, at a team level, co-workers tend to solve this challenge without outside help or pressure. Should we not simply make do with diverse perceptions of value across teams, and empower mediators between those groups, rather than diluting motivation under an autocratic so called 'shared vision'?
Facilitator: Stan Wade
The iconic Darwinist statement is now as compelling for complex organisations as it has been for living organisms. However, linking Agile to innovation, is taking a bold step further. In our Agile Treadmill series, we hinted that when industrialised, Agile actually incurs the risk of stifling innovation. Its obsession nonetheless, of speedily converting concepts into usable assets, meets a necessary, but not sufficient condition for innovation. This discussion will explore whether the political will to invest in a portfolio of initiatives, combined with governance mechanisms tracking success and failure at regular intervals, can create a ground where Agile and Innovation are mutually supportive.
Facilitator: Stan Wade
From a pure Agile perspective, the Programme Management Office (PMO) tends to undermine the alignment of accountability with responsibility. It intervenes in the collaborative relationships between those accountable for delivering an outcome and those sponsoring the delivery, resulting in poor decision taking, unnecessary risk and cost, and poor motivation in all project stakeholders. Still, some kind of function is required at a projects portfolio level, to prioritize the allocation of human and financial resources, and to act as mediation between projects protagonists and Enterprise Stakeholders. Should we name this function ‘the Agile PMO’ what would be its accountabilities and responsibilities?
Facilitator: Nigel Kneill
A common rhetoric at this year's Agile Business Conference was that Agile had become 'main stream' and was now a prevailing current of thought. What did people mean by this? Rightly or wrongly, Agile has predominantly been a bottom up dynamic. Operating primarily at the code and project level, zealous evangelists have promoted it as a panacea, as an article of faith with its inner-circle rituals. However, Agile’s underpinning dynamics of efficiency and risk management are equally attractive to Enterprise Stakeholders looking to unlock the value stream of major change programmes. Still ... with scale come compromises and politics. Can Agile successfully enter the boardroom and still come out recognizable to those who championed it in its early stages?
Facilitator: James Yoxall
The days of the technology focused CIO are long gone. The role of business leader is as important as the day job of ensuring the technology runs correctly. The day job is about developing capability to meet operational needs. The business leader works in collaboration with key stakeholders outside IT, to determine where to apply that capability taking into account priorities, risks and resources available. The ability to act responsively and effectively is a key component of the Agile mindset that helps the CIO to deliver both roles. This meeting will give peers the opportunity to share experiences of success and failure in these two complimentary areas, discuss how those can be characterised and, most importantly, predicted.
Facilitator: Chris Jones
Agile or iterative projects focus on frequent delivery of working software. This enables greater transparency by generating frequent early information about the capability of the project. Ideally, it also improves decision-making through better feedback. There are several challenges though. Firstly, the information generated by the project teams often requires translating and summarising in order to be relevant to sponsors and stakeholders. Secondly, if the information generated from the project is not what was hoped for then there can be a human tendency to "spin" or hide information. This meeting will invite peers to discuss ideas and share experiences on how to avoid those pitfalls and leverage Agile reporting to meet the requirements of business sponsors and Enterprise Stakeholders.
Facilitator: Benjamin Mitchell
Traditional "Supply of Goods" contracts make building a collaborative client/supplier relationship tough. The nature of the contract is to fix the requirements up front, agree delivery milestones and try to focus the team on delivering what has been defined up front. Given that being able to handle change and being responsive to customer's needs is the cornerstone of all agile and lean approaches to software development, how can a contract that actively discourages change help to build a long-term relationship with a supplier? Can IT procurement re-invent itself to push the boundaries of Agile beyond the enterprise and towards a community of partners?
Facilitator: John Wright
Using investment management techniques for the governance of IT delivery lifecycle is gaining a lot of traction. If anything, the ‘buy, hold or sell’ language is naturally engaging for senior business sponsors. At a deeper level, regularly bringing together key stakeholders during programme delivery to make decisions based on the value of IT spends, contributes to good risk management and quality assurance practices. However, IT projects are not self-contained financial products, and the knock on effects with their surrounding landscape can make a straight ROI rationale somewhat artificial to build. How can agile principles of value-based governance and stakeholder communication make the investment portfolio approach work?
Facilitator: Nigel Kneill
Corporate Culture is more often than not referred to as a hurdle for change. Indeed, the capability for complex organisations to constantly re-invent themselves seems constrained by cultural components such as behaviours, semantics or beliefs, and a reflection of those in their organizational and governance set-up. Can culture be purposely and directly influenced to make large organisations more agile, or is it merely an emerging by-product of innovative ways of working together within projects and programmes? Why bother about Culture?
Facilitator: Rob Smith
Agile relies heavily on concepts such as emergent design (where an overall design emerges while implementing small increments) and just-in-time design (where design is performed in parallel with implementation at the “last responsible moment”). Up-front architecture is not ruled out, but guidance is made on a sufficiency basis. This lack of a definitive approach often leads to key decisions about when and how architecture is done being based on the personalities involved. Can Risk—in all its guises, financial, technical, etc—be used as a focal point and arbitrator to drive effective governance and assess how much architecture and design is ‘just enough’?
Facilitator: James Yoxall
Traditionally, centralised IT departments have been focusing on economies of scale by pushing standards and rationalisation to the edges of complex organisations. There is an argument that this has often been at the expense of responsiveness and market intimacy. As a response, Agile lends itself to much more granular and decentralised organisational models, tacitly encouraging business stakeholders to regain ownership of programme delivery whilst pulling value from Corporate IT when needed. How can governance help accommodate the tactical efficiency of Agile with the strategic intent of reducing the IT chaos, and what role for Corporate IT?
Facilitator: Rob Smith
Agile comes with tons of literature on how to organise work at a very detailed level. How much of those activities are manifestations of an 'Agile Sub-Culture' aimed at integrating a growing workforce in need of a new religion? Can this relentless treadmill and its esoteric jargon stifle innovation and alienate the very people Agile purports to help? Is the mere adoption of behaviours and rituals without governance mechanisms intrinsically sufficient for supporting corporate goals and values?
Facilitator: Nik Silver
Implementing complex change programmes involves countless decisions at micro and macro levels. Whilst group decisions, by representing the perspectives of many stakeholders, typically lead to better decisions (than autocratic ones), they also imply a lengthier process which can defeat the purpose of efficiency. Whose perspective should then be included in which decisions to bring clarity and quality of thinking without diluting the fundamentals of leadership and accountability? The notion of 'value conversation' can prove a worthy guide for understanding the trade-offs between leveraging creative tensions within teams and recognising the need for separation of concerns.
Facilitator: Nigel Kneill
IndigoBlue's external view of the programme allied to the Agile approach proved invaluable.
There were three excellent presentations at yesterday's seminar Business Change in the Cloud, and an interesting question and answer session. Summary notes and the presentation slides are: