#75 out of 100

Posted on Leave a commentPosted in management

Although i am not acting as Agile coach or trainer but surprisingly listed here – 100 Top Agile Blogs in 2015TOP 100

Happy and proud to be among great people of agile community. It will definitely encourage me to continue sharing my ideas and thoughts about how to organize work in a company to keep Agile mindset even when you grow from 20 to 600.

Posts that worth taking a look at:

Thank you for reading.

Network structure – it works

Posted on Leave a commentPosted in management

It was a long journey of trying to understand what organisational structure is best for dynamic growth, experiments, agility and change.

Simple conclusion that i came up for myself – it works! And it is the best way to grow up to an organisation to a scale of 600 people at least. Reasons behind are simple – it allows you to scale fast naturally and have built-in flexibility in the structure to a constant change. Obviously there are challenges which you have to overcome.

TOP 7 Challenges

  1. Flexible structure is not possible if you want to keep technical foundation monolithic. Devops and Service Oriented Architecture is a must use practices otherwise organisation will not be able to adjust to changing business demand fast enough
  2. Easy to fallback to local optimizations and thinking that structure is something permanent
    • POD Leads and Keepers start to maintain status quo rather than to advocate the change as structure must be adjusted according new findings, growing number of people, speed of delivery and many other things that pop up during the journey
    • Extreme sense of ownership can lead to certain local optimizations instead of seeking global improvement
  3. It’s very important to define common artefacts for PODs as soon as possible so everybody knows what to expect and how to work. You can start from something simple first and grow it naturally according the needs
  4. Pod sponsor role is extremely critical in order to achieve alignment and solve challenges outside the scope of the POD or priority conflicts
    • Especially for service pods which are often understaffed and business value is indirect, but high expectations are formed by the community
    • Pod sponsor is an important contributor to network orchestration
  5. Transparency is key, especially regarding speed of delivery and commitments
  6. Behaviour and mindset is much more important than experience as new structure depends a lot on readiness to change and constant learning
  7. Change and adoption core group must be full-time activity and include decision makers (often C-level)
    • Plays leading role in network orchestration
    • Solves operational challenges together with leaders

But what you get instead:

  • you know value creation chain of your company and make dependencies visible
  • people are committed and motivated as they are the owners of what they do and decision making is delegated to them
  • problems are transparent to everyone who is looking for information and you can act upon them

Updated document with our experience – POD framework v.03, comparing to previous version you will find:

  • Description of deliverables and artefacts that can be used as a starting point of your journey
  • Better description of roles to handle expectations
  • Description of how roles work should together
  • Challenges that you must prepare for

If you have some experience building network structure would love to hear your insights, ideas and knowledge.

Question on errors and randomness?

Posted on Leave a commentPosted in management

Is it possible to build an organisation which benefits from uncertainty, errors and randomness?

reality

  • How small should be the teams? 
  • What should be minimum process?
  • What is the level of centralisation/decentralisation?
  • How often achieved agreements must be reviewed?
  • What behaviour is needed?
  • What is the ratio between explicit and self-discipline?
  • What is the level of autonomy?
  • Can growth be the target?
  • Should it reflect value delivery?
  • Should org. look different depending on the context?
  • Should unstable be new stable?

Those are curse words for any member in a company. Often companies are designed as if for any non-repetitive task it is exactly known what is going to happen and what is the most efficient way to do that.

The “science” in the science of …

Posted on Leave a commentPosted in management

Often notice that people tend to be “black and white” when talking about practices in any field, let it be management, design, development or whatever… e.g. go completely scientific and measure everything and be very structured or become completely ad-hoc and reactive.

contrast

Of course it’s an option to work in a binary way, but in my opinion it is not necessarily the best way to go while facing complex problem. You must have various “tools” in your toolbox and be creative in applying them depending on a situation or context.

As a confirmation for myself I’ve stumbled upon an article  recently which covers exactly the same topic – http://www.jnd.org/dn.mss/the_science_in_the.html

So, can design be a science? Sometimes yes, sometimes no. Can it be empirically based, evidence driven? Yes. Will it have to reply on intuition and the creativity of individual designers? Sometimes, yes.

Good – Cheap – Fast

Posted on Leave a commentPosted in management, quick thoughts

Good. Cheap, Fast! We all know that only two things can be picked, but always tend to forget that and spend lots of time and effort to have all three.

That is why it’s perfect decoration for a workplace, especially in the meeting rooms where you invite clients. It definitely can work as a reminder of this important truth.

good-cheap-fast
Good Cheap Fast