1. The term Lean is a Western invention. Taiichi Ohno said that putting a label on it meant that people would assume it came in a box, that you could simply unpack what was in the box and all would be well.

    In fact everybody's business is different. Deming talked about the need for method in the context of a deep understanding of how you work and what you need. He didn't have a list of the eleventy zillion types of waste, or a set of formulae to apply. Like all good coaches he went where the problem is and used his eyes. He looked at the connections between activities and the flow.

    More recently John Seddon has been commenting on what he calls the happy clappy toolheads obsession with standardisation, because it must be cheaper to have standard tasks, mustn't it? This ignores the variety in the incoming channels, which must first be studied. Then you can standardise on the incoming flow for each channel. The flow is likely different for different parts of the organisation, and a stalinist approach will fail and cause breaks in effectiveness. The method varies for each application, the only thing you should standardise is the approach.

    The talk will take a systems view of these problems, and present some of these ideas in more detail.

    # vimeo.com/76153864 Uploaded 107 Plays 0 Comments
  2. With the evolution and scaling of agile environment - there is a growing misconception amongst the leadership towards the need for consistency across teams. The moment we endeavour this worship for invariability - we lose sight and flexibility of true agile and lean principles. With the recent transformation of three teams within the same vertical - it was quite a challenge to maintain loose variability while satisfying the reporting needs of the top management. In this session - the speaker will share the approach that worked in collaborating across teams with a co-opetitive edge for higher performance. P.S: The interactive part of the session will require some physical movement in addition to team collaboration and role play.

    # vimeo.com/76159003 Uploaded 132 Plays 0 Comments
  3. Doing and learning is a cyclic process. That is, people learn during their work experience, and what they learn can be applied to their practice. Knowledge evolves during the process. People not only learn individually, but also collectively in a team working environment. This proposed talk presents a model of collective learning in team working environment, which is developed through my PhD research work. Collective learning is referred to how a group of team members interact with and learn from each other. A collective learning activity can be modelled as elements of input knowledge, learned knowledge, learning goal, rational trigger, and learning operators. These elements are linked with and interact with elements of a team activity (including input knowledge, output knowledge, and goal). Different forms of collective learning have been identified, e.g. one-to-one, one-to-many, many-to-one, many-tomany learning, assisted, joint learning, etc. The model is then applied to an agile software development environment to reveal the nature of collective learning in such an environment, based upon my past six years’ working experience as a software developer in a large international investment bank. The explanation of collective learning is illustrated with concrete industrial examples. The proposed talk is then concluded with some guidelines, aiming to enhance agile software development practices. In summary, the aims of this proposed talk include.

    Revealing the nature of collective learning in an agile software development environment.
    Serving a foundation to develop new guidelines, tools, and processes to support agile practices.
    Facilitating agile methodology practitioners (e.g. product owners, scrum masters, developers, business analyst, testers and business users) to reflect and rethink their current practices and to gain insights on how to run their agile team more effectively and efficiently.
    Providing some guidelines to enhance agile software development.

    # vimeo.com/76173016 Uploaded 63 Plays 0 Comments
  4. Agile is founded on people and interactions. This presentation will explain a model to align teams for high performance and give you practical techniques, adapted from clinical hypnosis, that have proven successful with project visioning, goal setting, improved team communication and business collaboration.

    Presented and facilitated by Irwin Fletcher and Stephen McAinsh from Calba, who have both led numerous change programmes, including agile, in the public and private sectors. Irwin is also a qualified Cognitive Behavioural Hypnotherapist and NLP Business Change Practitioner.

    # vimeo.com/76415113 Uploaded 50 Plays 0 Comments
  5. Information radiators are all the rage, we measure things, collect metrics and set targets as never before.

    But are we getting the full benefit? or are we inadvertently stifling progress, tampering and inviting dysfunction?

    Let's take a hard look at our love for measurement, how it can help us make better decisions, how we can use it to shape behavior & environment, and how we can with good intent fail miserably and wreak havoc.

    This session aim to challenge how we view metrics and data, their role in decision making and to provide an alternative framing to the problem of knowing what to measure.

    # vimeo.com/76475209 Uploaded 60 Plays 0 Comments

Lean Agile Scotland 2013

Lean Agile Scotland PRO

Videos from Lean Agile Scotland 2013

Browse This Channel

Shout Box

Heads up: the shoutbox will be retiring soon. It’s tired of working, and can’t wait to relax. You can still send a message to the channel owner, though!

Channels are a simple, beautiful way to showcase and watch videos. Browse more Channels.