What Do Agile Teams Need to Know?

What Do Agile Teams Need to Know?

What should a team member and the team know?

I asked several people covering a range of experience concerning an agile way of working in a few organizations in different industries what they felt agile teams needed to know.?It was all very informal, just a way to get some insights and gather my thoughts before discussing @Al Shalloway and @Steve Tendon in our weekly UN-Common Sense live stream.?

What I gleaned from asking that simple question was something I did not expect, and on reflection, I think it may stem from the word “agile” team.?The majority of the replies I received centered on knowing things related to a timeboxed approach.?Whether “sprint” or “iteration,” almost all the replies were in the realm of timeboxes.?Few responses included flow - a lean-approach.?Did your first thoughts focus on an iterative approach and things to know that would support success when looking at the title??Please share your thoughts in a comment.

The item at the top of my list of what agile teams need to know – they have options. So often, the first steps as an individual and as a team member center around a mostly pre-defined path to an agile way of working.?For good or bad, Scrum and the Scrum Guide are the vast majority of where most start.?Unfortunately for many, they never have the opportunity or seek out other options.

Al, Steve, and I, along with those watching the live stream sharing, had excellent items.?The following is a selection of a few that I felt are a great starting point for anyone to reflect on or discuss with others:

  • You have options
  • Where to start
  • Agile includes both iterative and flow (lean) approaches
  • How to continuously improve
  • They should challenge/check everything they do for better ways of working (single vs. double-loop learning) - nothing is “scared”
  • Have autonomy, but they need to know that their contribution to the value created for the customer is not ALL of the work to create that value
  • Know how their work contributes to the value produced and how it fits in with upstream and downstream value-adding activities that are also needed
  • That there is no one approach or an ideal approach, the choices that a team makes today may need to change tomorrow based on the context of their situation
  • Understand the objectives of the practices and techniques they choose to use – the “why”
  • Know that as knowledge workers, they choose how best to get their work done

The following link to the recorded live stream on this topic for additional insights:

https://www.dhirubhai.net/video/live/urn:li:ugcPost:6828011190040436736/

No alt text provided for this image
Michel Thiry, PhD, PMI Fellow

Managing Partner, Valense Ltd. | Strategic Consultant | Author | Speaker | Team Coach | Dyslexic Thinker

3 年

Joshua Barnes, really good read and important points, looking forward to listening to the discussion. I believe the main comment I see in your summary is: "Unfortunately for many, they never have the opportunity or seek out other options." You relate it to SCRUM vs Lean, but I would expand it further and say that most project managers practicing in a predictive context never had the opportunity to experience agile and vice versa. Note that I said "practice", not "read on", and sadly, this has created an "us and them" mentality on both sides. If I had one suggestion to make, it would be that every process focused project manager should work on an agile team at least once and every agile team member should work on a predictive project at least once before they berate each other. There is much to learn and to experience in both areas and the more understanding we will gain, the better we will be able to choose our WoW. ??

要查看或添加评论,请登录

社区洞察

其他会员也浏览了