Agile SOW

Software projects are becoming increasingly complex. This complexity demands Agility. Agility translates to faster product increments, shorter review cycles, end-to-end picture of the product which essentially means incremental and iterative delivery. Quality needs to be built in. End user and customer engagement (via the PO) is indispensable for both building the “right product” and the “product right”.

While the IT operations are going through a paradigm shift towards Agile, has the documentations such as SOW  changed to cater the needs of Agile world?

What is an SOW ? Statement of Work (SOW)  is a legal binding contract between  an Organization and a contingent worker or a vendor that dictates the directions of how the work will be done. So, for Agile projects, the less you write, the better off you are. Remember, the mantra is: “Less is more”. Having said that, an SOW for an incrementally-delivered project should consider the following facts when drafting one.

  • What system are you trying to build? What are the common objectives? Describe the system. Include lists of themes, (feature) areas and any other important descriptions that help both the parties to understand the system better.
  • Declare – loud and clear – that our development strategy is incremental and iterative.
  • In Agile, neither of the parties know up front 100% of features that will constitute the final system. We negotiate that with the product Owner (PO) on an ongoing basis
  • Establish the  fact that features will be delivered incrementally in an iterative fashion called sprints. Define the sprint. A Sprint may range anywhere from 1 to 4 weeks of iterative cycle.
  • The PO, business stakeholders and customer can review what has been created and provide valuable feedback at the end of each sprint to refine and re-prioritize for upcoming iterations.
  • The project sponsor has the power to cancel the project should he/she see no further value in building this product. There should be a working agreement on how much advance notice the sponsor needs to provide to the development teams and it should ideally apply at the end of an ongoing sprint
  • The customer/PO can choose to change the pace of delivery by changing priorities of upcoming features based on the review of product increment.
  • The customer/PO cannot change the pace of delivery by demanding to cut corners (quality). In other words cutting out features/MMF is fine but delivering everything at a tighter pace by cutting upon quality is not acceptable
  • Elaborate on what to Expect from the team. Include an initial delivery plan of features that the customer can expect from the team in the first 2 to 3 sprints in the order of priority. If possible, It is good to provide the vision, product backlog (top 3-4 sprints prioritized with 70-80% accuracy.

Including a Release plan in SOW

The SOW can include a statement that as the teams start working, they will put together a release plan to provide an insight on how the timelines look at this time. A note in bold must indicate that this is how it looks at the very beginning and that this release plan will be updated after every sprint and the updates will be made available to all stakeholders. The release plan should try to cover the below facts:

  • Top 3-4 sprints with updated items(from the initial plan)
  • Next 8-10 sprints prioritized with 50%-60% accuracy. Then, next 6-8 sprints could be with even lower( 30-40%) accuracy and the remaining items prioritized with 20% or lower accuracy.
  • The PBI (product backlog items) should map to the product roadmap. The product roadmap should also have releases marked with farther out releases having increasingly lower accuracy (confidence rating)

Initially the big blocks of work lower in the backlog will be Tshirt sized and the teams may want to have a rough mapping of Tshirt sizes to get an arbitrary value of story point . Alternatively, affinity sizing can be used to quickly and roughly estimate a large initial backlog so the teams have some numbers to refer to as they take strides into sprints With time, as the product emerges and evolves, the PO and stakeholders get better sense of the timelines with updated release plan which has estimates with higher accuracy The team velocity is an important factor for creating the release plan. Prediction of team velocity is possible after first few sprints. A team’s velocity is not same as any other team’s due to various factors like experience, number of members in team, complexity of product, the technology they are working on, their style of estimation, etc. Velocity plays an important role in Agile release planning. Proper coaching by a servant leader Scrum Master is highly essential for a Scrum team to estimate consistently, plan and commit to correct capacity and then deliver to its commitment. This brings up a stable velocity and predictability which in turn provides confidence to the PO and stakeholders and they look forward to the updated release plan Agile at the end of every sprint. Servant leader Project managers and Scrum Masters must include only the details in SOW that are of Agile nature. There should be no pressure from the leadership to include details that SMs/PMs do not feel confident about. This way the Servant leader SMs won’t be held hostage by not accomplishing timelines and scope they did not think could realistically be included in an Agile SOW. The behavior of the leadership in such companies that want to really adopt a more Agile way of working should be transparent and oriented towards creating a culture where their actions are in sync with their desire to be Agile 

Final Notes

   Let your SOW be versioned and wait for the signatures till an agreed upon Agile SOW is in place.  The first version of the SOW should be light. A small handful of sentences should suffice. If you do get push back, review your options, some of which could be: 

  • If it’s not win-win, educate and coach the client on why Agile contracts are more applicable to how you are working today. Walk away from the deal if there is strong insistence in signing a traditional SOW 
  • Suggest to the client on creating a non-legal working agreements document on how both sides can work together. What are some of the expectations that each side can fulfill to the best of their efforts? Example: The Agile Scrum dev teams can provide updated release plans, deliver to their commitments (80-100% of planned work), etc. The client should build trust as the teams are delivering with a stable velocity and understand that if updated release plans show slowness, it’s because more accurate information is available now 
  • This is not a great option but Agile companies still do it. Give in to the demand of the client and add fixed date, fixed scope deliverables and be prepared to work extra hours for free when things have to be reworked 
Amitabh (Amit) Sinha is a servant leader entrepreneur, visionary, mentor, trainer and coach. Amit is highly passionate about Agile, its principles, values, and the human side. Amit is a people champion and strives to bring out the best in his teams. Amit leverages his expertise in Agile, Scrum, Kanban and people skills to increase team effectiveness and happiness. See more
0 0 votes
Article Rating
Subscribe
Notify of
guest

0 Comments
Inline Feedbacks
View all comments

EXPERIENCE AGILE. START TODAY

0
Would love your thoughts, please comment.x
()
x

Enter E-mail Address

We promise to keep your email address safe. You can check our Privacy Policy.

Patrick Foster

Agile Coach


Patrick Foster

I’m a leader who serves as an Agile Coach in organizations.

I help senior leadership plan long-term strategic decisions while embracing the Agile mindset.

I also work with teams to help them become self organizing on their journey of providing value to the customers.

I see my clients as creative, resourceful, and whole and I’m here to walk alongside them to achieve business outcomes.

Elena Vassilieva

Innovation Leader Coach & Agile Transformation Adviser

Elena Vassilieva is an executive leadership coach who uses virtual reality (VR) and artificial intelligence (AI) to facilitate sustainable and immersive feedback for conscious leadership development. Elena integrates principles of Conversational and Emotional IQ and Systemic Team coaching with an Agile/Lean empirical approach to create a personalized holistic coaching
experience. Drawing on her years of training, mentoring, and coaching executives and teams in Agile transformation, she now serves as a trusted advisor for thought leaders who engage in digital transformation.
Elena is an experienced people development leader known for her ability to creatively align business strategy to people’s practices while keeping a passionate focus on workplace culture and values.
Elena is an ICF Certified Coach, ORSC, and AoEC Certified Systemic Team Coach, Certified Visionary Leadership Coach.
As the Scrum Alliance Certified Coach and Certified Agile Leadership Educator, Elena is teaching, training, and coaching teams and individuals to become great Agile professionals and Agile leaders. She brings together diverse and passionate voices dedicated to developing thriving workplace cultures, creating joy and value with the Agile approach, and embracing the agile mindset in work and life environments.
Elena works with leaders and teams around the globe, helping them engage in digital transformation and mapping out powerful organizational shifts to create a sustainable culture focused on learning and innovation. She helps executives in global companies find alignment around cultural and social diversity and aligns around shared purpose, shared values, and business goals.
Elena blends her diverse experiences as a trusted advisor, professional consultant, coach, researcher, and VR documentary producer.

Alireza Boloorchi

PhD in Computer Science

Alireza Boloorchi is passionate about efficiency for the whole. He believes leadership is about the courage in sacrificing localized efficiency for a greater goal. For the last 12 years, he has been helping several large and small organizations to adopt/adapt more efficient process using Agile/Lean values and principles.

He received his PhD in Computer Science and is Certified Scrum Professional by Scrum Alliance. His experience is rooted in software engineering followed up in roles such as Scrum Master, Agile coach, ENT Agile coach, and leadership in Agile organizations.

He has worked/consulted in several industries such as Finance, Game, Semiconductor, manufacturing , etc. Academia has been an important part of his professional life, and He is researching and teaching Agile in the academia as an Adjunct Professor at Oklahoma State University. And serves as reviewer for several journals such as Journal of Super Computing, Network Systems, and Information Science.

Zach Bonaker

Benevolent Trouble-maker

Zach Bonaker is a “benevolent trouble-maker” based in San Diego, California, USA and has more than 10 years of experience assisting organizations with achieving their goals through improved working conditions and team-centric systems of work. With experience guiding Fortune 500 companies to multi-million dollar startups, Zach draws upon agile principles, relationships, and systems thinking to redesign structures into safe, collaborative environments. Zach is an international conference speaker, frequent podcast guest, and contributor to the global agile community. When he isn’t thinking about next-generation agile ideas, Zach can be found enjoying the sunny California weather and connecting with people all over the world.

Michael de la Maza

PhD, MIT, CEC, Co founder Demingway.com

Michael de la Maza is the founder of Heart Healthy Scrum and a Scrum Alliance Certified Enterprise Coach (CEC). Previously, he was VP of Corporate Strategy at Softricity (acquired by Microsoft in 2006) and co-founder of Inquira (acquired by Oracle in 2011). He is the co-editor of Agile Coaching: Wisdom from Practitioners and co-author of Professional Scrum with TFS 2010 and Why Agile Works: The Values Behind The Results. He holds a PhD in Computer Science from MIT.

Jeff Patton

Chief Troublemaker

Jeff Patton helps companies adopt a way of working that’s focused on building great products, not just building stuff faster. Jeff blends a mixture of Agile thinking, Lean and Lean Startup Thinking, and UX Design and Design Thinking to end up with a holistic product-centric way of working. Jeff is author of the bestselling O’Reilly book User Story Mapping which describes a simple holistic approach to using stories in Agile development without losing sight of the big picture.

Jeff’s a Certified Scrum Trainer, and winner of the Agile Alliance’s 2007 Gordon Pask Award for contributions to Agile Development. You can learn more about Jeff, and find essays and past writing from his columns with StickyMinds.com, Better Software Magazine, and IEEE Software on his website: jpattonassociates.com. 

Amitabh Sinha

Execution Strategy Advisor, CTC

Amitabh (Amit) Sinha is a servant leader entrepreneur, visionary, mentor, trainer and coach. Amit is highly passionate about Agile, it’s principles, values, and the human side. Amit is a people champion and strives to bring out the best in his teams. Amit leverages his expertise in Agile, Scrum, Kanban and people skills to increase team effectiveness and happiness.

Amit has had huge success in transforming teams, departments and organizations. He has led, coached, nurtured and trained hundreds of teams into high performance and happiness! Amit’s teams have often been noted for their high levels of exuberance. Amit helps Scrum Masters, Product Owners, leaders and executives understand the Agile mindset and how to create effective products that delight customers. 

Amit contributes to the community by speaking at various forums and meetups to share his knowledge and wisdom with others. He delivered a popular workshop on happiness and productivity at the global Agile conference August 2019(AA 2019, DC). Amit lives with his wife and three boys in Palo Alto, California.

Rakesh Sadhwani

Business Strategy Advisor

Rakesh Sadhwani is an entrepreneur, businessman, and technical leader who possesses a wealth of industry experience and know-how.  He currently serves as the CEO of an award winning, Bay Area technical staffing and solutions firm, Vertisystem. Rakesh’s expertise includes on-shoring and off-shoring, staff augmentation, business strategy, business development and creating valued partnerships.

What sets Rakesh apart as a leader is his dedication to the relationship first, his genuine commitment to the community, enabling his staff’, and a commitment to doing what is right.  Rakesh is a true partner who sincerely listens and endeavors to deliver value above and beyond your expectations. Rakesh lives with his wife and two daughters in Fremont, California.