Agility is about culture and mindset. How much of that is impacted by the set up and the structure of the organisations?

I'll explore and share experience on the few practical differences and the differences in outcome in:

- coaching stable teams over project teams

- scaling with chapter coaching over team coaching

- coaching leadership teams / leaders over team coaching

- instructional coaching over back of the room coaching (in the initial stages)

And I'll share some of the instruments I've used that can be useful. I'd like to keep it interactive with questions.

 
2 favorite thumb_down thumb_up 0 comments visibility_off  Remove from Watchlist visibility  Add to Watchlist
 

Outline/structure of the Session

Introduction

Exploration into topics

Questions and Answers

Learning Outcome

Better appreciation of the systemic challenges in agile transformation.

Target Audience

Anyone. It will be useful if you are already familiar with some concepts in agile.

Prerequisite

Reflect on existing agile transformation challenges and prepare questions.

schedule Submitted 1 week ago

Comments Subscribe to Comments

comment Comment on this Proposal

  • Liked Steven Mak
    keyboard_arrow_down

    Steven Mak - Temporal Modelling

    Steven Mak
    Steven Mak
    Ugly Code Cleaning Dude
    Odd-e
    schedule 1 week ago
    Sold Out!
    100 mins
    Workshop
    Beginner

    Domain Driven Design, DDD emphasize communication with domain expert to build models and hence make software. How do we start with modelling? Starting with objects? Relationship between objects and the world? Architecture? Object Oriented Design is very readable in static world. However, it looks like OO model becoming limited when it deals with interaction and events. Ideas like CQRS and Event Sourcing are based on time and events. In reality, inside an enterprise, we also see work flowing between departments and people. Event Storming Workshop is trying to see the events and process in a domain model.

    In addition, this workshop we shall explore the implications we shall have with software design, and relationship with other agile practices.

  • 100 mins
    Workshop
    Beginner

    Improv your coaching skills (pun intended) and your team performance! On a superficial level, improv techniques introduce play and fun into every team. On a deeper level, it helps you create a culture of safety, experimentation and true collaboration. It helps people to welcome change, uncertainty, open up and helps infuse teams and individuals with a dose of EQ. It also helps you to improve your own coaching skills! Wanna know more? Come and find out! This workshop will introduce you to improv by throwing you heads-first into one exercise after another.

  • Liked Jas Chong
    keyboard_arrow_down

    Jas Chong - Product Owner / Scrum Master - Grow your own

    Jas Chong
    Jas Chong
    Agile coach / Scrum Master
    IBM
    schedule 1 week ago
    Sold Out!
    45 mins
    Workshop
    Beginner

    For an organisation undergoing agile transformation, some of the initial biggest people challenges are around creating new agile roles and finding the talents to fulfilling these roles. The most prominent of the challenges are product owners and scrum masters. Like many organisations, the most immediate strategy is to hire and they often end up with people who are short on industry knowledge, pre-existing agile practices and knowledge that are not aligned or unable to hire. Very often, organisations appoint within internal organisations but fall short on how to find them and how to grow them.

    This is an interactive workshop on how to identify and develop competences for product owners and scrum masters. It can be adopted to your organisation's existing competency programmes. In this exercise, I'll be using Strength Finder cards.

    I'll also provide some tips on how to scale by equipping the right product owners and scrum masters and growing them.

  • Hien Nguyen
    Hien Nguyen
    Board member
    Agile Vietnam
    schedule 3 weeks ago
    Sold Out!
    45 mins
    Talk
    Intermediate

    How is your Agile team? More line of code? Less bugs found?... Your Agile team is performing well? Not really.

    Organization always concerns about how to measure a team when they adopt Agile. There are some misconceptions about the Agile team measurement that lead to the wrong organizational behavior. This session defines the ideas of team measurement in both view of team and organization.

  • Liked Pondd Suwitcha Sugthana
    keyboard_arrow_down

    Pondd Suwitcha Sugthana - MASTERING CUSTOMER JOURNEY: creating artifact to bind the team

    20 mins
    Talk
    Beginner

    "What are we building? And why?"

    "I need this info! Where do I get it?"

    "I've got a lot of user research, what's next?"

    Chances are you will hear these words from your team many times in any project.

    Is your team making wasteful decisions because they didn't have a common understanding - especially across different roles? Is your team slowing down because the knowledge and decisions are owned by just a few key people? And what if some of these key people who own the knowledge take a vacation when you most need them?

    In this talk you will learn how convert all the great user insights you gathered and discovered into easy and actionable items that your team can use to move your project forward.

    You will learn to:

    - Externalise knowledge from your team
    - Consolidate and align vision
    - Create a core onboarding journey
    - Make better user of empathy
    - Understand "as-is" state and how to drive to an ideal "to-be" state

  • Liked Steven Mak
    keyboard_arrow_down

    Steven Mak - Mentoring Technical Practices

    Steven Mak
    Steven Mak
    Ugly Code Cleaning Dude
    Odd-e
    schedule 1 week ago
    Sold Out!
    45 mins
    Talk
    Intermediate

    My interest is to help developers adopt technical practices and being a mentor has played a big part. Through the years I've tried many ways to maximise the effectiveness of mentee's learning and also brings many challenges and discoveries. In this talk, I'll share my learning journey and hope it'll inspire you to help others improve their technical practices.

  • Liked Hien Nguyen
    keyboard_arrow_down

    Hien Nguyen - You need weekly release, include mobile

    Hien Nguyen
    Hien Nguyen
    Board member
    Agile Vietnam
    schedule 3 weeks ago
    Sold Out!
    45 mins
    Case Study
    Intermediate

    One of the main point in Agile software development is continuous delivery that Scrum states it Sprint. When the delivery benefits to user, it becomes continuous release. With DevOps, the continuous release becomes easier and many teams can practice it today with web application.

    But mobile is another story. We cannot have failover, we cannot have rollback… to react to the mistake. App Store review takes time as well. So while mobile first is a trend but so few organization can get continuous release happened for mobile. How to practice the weekly release for mobile app?

  • Liked kyon_mm
    keyboard_arrow_down

    kyon_mm - Scrumが難しいのは幻想 -情熱の再定義-

    kyon_mm
    kyon_mm
    Test Architect
    オンザロード
    schedule 3 weeks ago
    Sold Out!
    45 mins
    Experience Report
    Intermediate

    私達のチームは2016年までメトリクスの活用、スプリント期間の短縮、くじ引きで決めるPOやSM、などのプラクティスを通して改善を繰り返してきました。スクラムガイドもどんどん破りました。

    このチームはScrumが難しいなんて思っていませんし、誰でも出来ると信じています。

    チームが開発する製品は大きく変わりましたがScrumが難しいなんてことはありませんでしたし、

    なによりこのチームのエッセンスを大学生40名に導入したところなんと1週間で1日スプリントをモノにしました。Scrumが難しいのは幻想だったのかもしれません。

    我々のチームはこういったことを通して2017年にいくつかのプラクティスを確立しました。スプリント期間は1時間へ、チーム内ボトルネックへの対応時間は25分以内を保証、人的リソース活用の損益分岐点を常に意識できる開発プロセスです。

    結果、1週間でレビューを35回以上、振り返りを30回以上行っています。1週間で改善した項目は最大で20アイテムにおよび、それらのムダ取りによって6ヶ月間で最大2倍の成果を生み出しています。

    チームのパフォーマンスを最大化するために私達の計画的な学び方、偶発的事象からの学び方などをScrumの文脈でご紹介します。

  • Liked Terry Yin
    keyboard_arrow_down

    Terry Yin - 6 Years Of Teaching Certified Scrum Developers: Re-spec, Re-design & Re-entry

    Terry Yin
    Terry Yin
    Programmer
    Odd-e
    schedule 1 month ago
    Sold Out!
    45 mins
    Experience Report
    Beginner

    Every time we did our 5 day Certified Scrum Developer class, it's a rich learning experience for both us and the clients. After doing it for 6 years and also practicing what we teach, I've summarised the topics into three rhythmic steps, which I "dance" over not only during my CSD classes but also in other technical coaching situations, again and again. I call these steps Re-spec, Re-design and Re-entry.

  • Liked Ryutaro YOSHIBA (Ryuzee)
    keyboard_arrow_down

    Ryutaro YOSHIBA (Ryuzee) - Scrum プロジェクトの開始におけるベストプラクティス / Best Practice for Initiating Scrum Project

    45 mins
    Talk
    Intermediate

    Scrumではプロダクトバックログを用意し、そこからスプリントが始まることが前提になっています。しかし新たなプロダクトやプロジェクトを開始する際には最初からプロダクトバックログが用意されているわけではなく、ほかにも準備をしなければいけない項目が多数あります。本セッションでは最初にスプリントを開始する前までにやるべきことを過去のコンサルティング事例を踏まえて解説します。

    Scrum assumes that there's a product backlog and then sprints can be started from there. However, when starting a new product or project, the product backlog is not prepared yet from the beginning, and there are many other items that must be prepared. In this session, I will explain what should do before starting sprint #1 based on my past consulting experience.

  • Liked Miho Nagase
    keyboard_arrow_down

    Miho Nagase / Tatsuya Sato - とにかく明るいセッション

    20 mins
    Workshop
    Beginner

    え、え、え、ちょっと待ってちょっと待って?

    このセッション、明るくなーい!???