Business Complexity Points - A framework for normalizing software complexity and reaching consensus on requirements

What if you had a framework for building the right things better and faster?

 We know scope management issues in software projects always have the potential to impact business outcomes and also severely damage a good rapport with stakeholders. The majority of challenges in scope management are consequences of inefficient communication, poor management of expectations and weak scope assumptions to support estimates & planning and, consequently, negotiations with clients.

 Although this is not exclusive to agile projects, it has always been vigorously debated within the global Agile Community. In order to support fair agreements, effective planning and the delivery of better solutions without giving up the agile mindset, people have always been eager for better ways to understand and reach consensus on business requirements and scope in agile projects.

In this session, I’ll share a technique we've developed to normalize scope and requirements comprehension. It has been proven effective not just to overcome all those challenges but also to determine software size in terms of functional complexity and enable a data-driven foundation for continuous improvement. We’ll share details of this framework including: how it was conceived, why its useful to address such challenges, how it works and how to apply it.  See real case examples where the method has been successfully applied as well as further benefits such as support for estimates and the foundation for data-driven performance demonstration and continuous improvement. Finally, we’ll invite you to engage and support this framework.

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

Outline/structure of the Session

  • Section 1 - introduction and motivation, challenges commonly observed when clients have to deal with scope definition and to reach consensus on requirements in Agile engagements, and all the lessons we have learned while trying to solve them.
  • Section 2 - details on the framework we developed - the core objective of this session - including: how it was conceived, why and how its useful to address such challenges, how it works and how to apply it.
  • Section 3 - real case examples where the method has been successfully applied.
  • Section 4 - further benefits this method can provide, such as an important support for estimates and the foundation for data-driven performance demonstration and continuous improvement.
  • Section 5 - how to engage and support this framework.

Learning Outcome

  • A lean technique to enlighten business requirements in a natural way, reaching depth in understanding and working to maximize consensus with customers;
  • A new approach to normalize software complexity/size that will effectively enable you to define and communicate scope agreements in agile engagements while allowing you to benefit from a flexible & adaptable mindset;
  • How to benefit from size normalisation to create a data-driven foundation and enable objective performance demonstration and continuous improvement for your agile projects.

Target Audience

Agile team members, Project Managers, Product Owners, stakeholders and anyone involved on sprint and product backlog prioritisation and related discussions

schedule Submitted 1 year ago

Comments Subscribe to Comments

comment Comment on this Proposal