Agile Boost Camp - Accelerate your path to a healthy and sustainable Agile Process

So, you started adopting Agile practices, maybe you took a course or read some books and articles and decided to jump into the water. Good for you! However, you quickly realize things don’t work the way they used to. It feels like chaos, it is typically painful and frightening and you have many questions and concerns. Over time, you might find a way of working that makes sense, but most likely, you will still stay stuck with some of the pains or avoid challenging some of the things that do not allow you to become truly Agile.


In this workshop we will leverage our vast experience with AgileSparks clients all over the world to provide participants with practical tips and tricks, patterns and anti-patterns and good practices that can accelerate your path to a stable, healthy and sustainable Agile way of working as well as boost your performance.




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

Outline/structure of the Session

The agenda includes a long list of useful advice and practices that will be covered through theory and hands-on exercises, but will also be highly interactive. Participants will be expected to bring in challenges from their day-to-day work and time will be allocated to go over these challenges and provide skills and know-how participants can apply in their workplace immediately. 

  • Introduction and Expectations - create the workshop "Agenda Kanban" and collect situations from the participants
  • Introduce the various "boosts"/"patterns" on the "menu" for the workshop
  • Map collected situations to the "menu"
  • Prioritize the backlog/"menu" - while learning useful, fast and fun interactive decision making techniques
  • Go into timeboxed sprints each covering an item from the backlog and getting it from the backlog all the way to "epiphany + possible action"
  • Include some "lightning-mode" sprints where items are covered very quickly
  • Summary and Takeaways for each one of you based on the ideas you got
  • Retrospective and Closing

 

Learning Outcome

The participants will prioritize which smells/dysfunctions/problems to deal with in the workshop:

  • How to deal with “Scrum-fall” of uneven flow within the sprint
  • How to avoid "planning hell" and shorten the time and effort spent in planning/estimation
  • Commitment vs Agility - how to bridge the gap between the need to commit to a certain date/scope and Agile and how to do Agile Release Planning
  • How to deal with big stories
  • How to effectively do testing on an Agile project
  • How to deal with situations where you cannot have a full “Shippable Software” every sprint
  • How to avoid growing quality problems/gaps due to pressure to deliver / focus on the short term. How to avoid and handle Technical Debt and work in a Sustainable pace.
  • How to deal with rework/waste caused by working in small stories
  • How to reduce the number of defects and surprises in An agile environment? Test-First, ATDD/BDD as a way to Build Quality In
  • How to avoid being blocked during the short sprint due to missing information - the concept of READY
  • How to avoid the retrospective dying off due to lack of impact/interest
  • How to maintain energy within the team in the long run
  • How to deal effectively with external resources/people that are shared amongst multiple teams
  • How to deal with situations where the classic fixed Scrum team doesn’t seem to work
  • How to see the big picture beyond the sprint
  • How to see what is really going on inside the sprint, find bottlenecks, and focus the team on addressing them
  • How to help the team grow its capabilities in a way that creates better redundancy and velocity while still expecting them to self-organize and pull the work autonomously? The Skills Matrix concept and how it can be used by teams to align on skills growth targets
  • How to make sure your meetings are effective, especially your Agile ceremonies? Facilitation techniques and specific tips for Agile meetings
  • How to adjust the Agile ceremonies to the situation of several teams working together? Panoramic activities and specific tips and tricks at scale
  • How to align Agile and the HR policies of the organization? Agile Performance Reviews, etc.
  • How to manage and monitor risk throughout the project
  • Visibility, dashboards, measurements – how to define, using the right amount
  • How to deal with various Scrum "Smells"/Scrumbuts? How to recognize them

Target Audience

Practicing Scrum Masters, Development Managers, Team Leads/Managers, Lean/Agile Coaches/Consultants, Program/Release Managers, Change Agents - All with at least 6 Months experience on a real agile team/project

schedule Submitted 2 years ago

Comments Subscribe to Comments

comment Comment on this Proposal

  • Liked vinaya muralidharan
    keyboard_arrow_down

    vinaya muralidharan / Sutap - The Snowball Effect - From Team Kanban to Enterprise Kanban

    20 mins
    Experience Report
    Intermediate

    About two years ago, we embarked on our journey towards Agility and Kanban was our vehicle.

    But Kanban had people worried.

    How can we not have detailed plans?! How can we limit WIP when we have so many things to work on?!

    We have due dates to meet! And so on.

    We would like to share one of the approaches that we adopted to help move the change along.

    In addition to focusing on the Kanban implementation at the project levels, we adopted another route – to work through the individuals and the teams – a grounds up approach. We encouraged people and teams to use Kanban boards to manage their daily tasks.

    You have difficulty in managing personal stuff? We’ll help you manage better!

    You have issues in managing team level priority? Look what we did within our team- we have a Team Kanban and we are now much better organized!

    One by one we saw people getting interested. The movement gathered steam - we worked directly with a handful of people and they in turn got their peers onboard. And we saw various flavors like Personal Kanban, Team Kanban cropping up all over the place – even in our Travel Office and Corporate Office. What this did was give people a safe, controlled environment to experiment and learn in.

    As they got used to the ideas of limiting WIP, pulling work, visualizing work and “stop starting, start finishing”, it gave them the confidence to work this way at the project level too. And it made our lives as change agents just a wee-bit easier!

    We welcome you to come hear our story about nurturing the change towards Agility by making it a grass roots movement.

    A brief introduction to Amdocs - Amdocs is a leading provider of Customer Experience systems and services in the telecommunications domain, typically doing large scale transformation projects.

  • Liked Hrishikesh Karekar
    keyboard_arrow_down

    Hrishikesh Karekar - An Empirical Approach to Agile Transformations

    Hrishikesh Karekar
    Hrishikesh Karekar
    Agile Coach
    Amdocs
    schedule 3 years ago
    Sold Out!
    20 mins
    Talk
    Beginner

    Enterprises big and small are aspiring for agility these days and kick-starting Agile transformations. Agile is mainstream. The movement that started with a manifesto and principles has grown bigger. From product development and startups, agile is now being adopted in mainstream (read legacy) companies for all kinds of knowledge work beyond the scope of pure product development – in services, support, marketing, HR and so on.

    With the widespread application, many ways to achieve agility have also sprung up. We have ScrumKanbanScrumbanSAFe and probably few more variations. Each have their benefits and challenges depending on the organizational context that they are being used into.

    For organizations that are just starting, this plethora of information is quite confusing and intimidating sometimes too. Transformations also involve a lot of investment - both financially and otherwise. Its a big change. Deciding on an approach at the outset is not trivial. 

    The talk would suggest an approach to Agile transformations that is based on the fundamental premise of Agile - the empirical philosophy of transparency, inspection and adaptation and provide practical tips and tricks based on my experience with large scale transformations.