Agile is so much more than rituals and buzzwords, but often the real value is lost as organizations focus more on adhering to processes than the reasons behind them. Teams all too easily fall into the trap of following a prescribed method and deviate little from that original template. A continuous improvement approach implies a team is regularly questioning, tweaking, and iterating on its own version of Agile. Today's set of practices and processes should not be identical to those from a year ago.

Join Blake Nyquist and Wade Wachs for a discussion on Agile thinking and how to break out from a fixed set of processes. You will leave this session with an increased understanding of how Agile practices can and should be useful, along with ways to focus on their value in your organization. Bring pains points from your own Agile efforts to discuss with others in the session and take actionable suggestions back to your team on Monday.

 

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

Outline/structure of the Session

- Introductions (5min.)

- History of Agile at Liquid Web (15min.)

- Interactive segment: Identify your Agile pains (20min.)

- How Agile practices become stagnant or broken (15min.)

- Interactive segment: Choose a next step to break out of your Agile rut (20min.)

- Q&A (15min.)

Learning Outcome

- How do you identify "smells" that may indicate a process is not being as effective as it could or should be?

- What are tools to help break out of dogmatic thinking or blindly following a process?

- What is the very next step you can take to improve your Agile situation?

Target Audience

Any member of an Agile team or organization

schedule Submitted 3 years ago

Comments Subscribe to Comments

comment Comment on this Proposal

  • Liked Matt Heusser
    keyboard_arrow_down

    Matt Heusser / Wade Wachs - Save Our Scrum

    60 Mins
    Workshop
    Intermediate

    Ken Schwaber, a co-creator of scrum, says that only 25% of teams trying Scrum actually realize the gains they had hoped for. Another informal poll shows teams callling themselves "Scrumbut", "Scrumerfall", or "Scrumish" than actually claim to successful!

    It is as if something conspires to make Scrum ineffective. 

    Let's get real. Scrum is designed to expose problems. It does not, by itself, solve the problems. In theory, Scrum provides a framework for the team to work through the solution themselves. In practice, politics, rhetoris, and lack of training often get in the way.

    This talk is about understanding common Scrum problems and breaking through ruts.

    In this conversation Matthew Heusser and Wade Wachs will discuss the heart of Scrum, where it goes wrong, how testing can enable Scrum success - and how team members can improve their visibility and role while contributing to Scrum and team long-term success.