ThoughtWorks
  • 联系我们
  • Español
  • Português
  • Deutsch
  • English
概况
  • 工匠精神和科技思维

    采用现代的软件开发方法,更快地交付价值

    智能驱动的决策机制

    利用数据资产解锁新价值来源

  • 低摩擦的运营模式

    提升组织的变革响应力

    企业级平台战略

    创建与经营战略发展同步的灵活的技术平台

  • 客户洞察和数字化产品能力

    快速设计、交付及演进优质产品和卓越体验

    合作伙伴

    利用我们可靠的合作商网络来扩大我们为客户提供的成果

概况
  • 汽车企业
  • 清洁技术,能源与公用事业
  • 金融和保险企业
  • 医疗企业
  • 媒体和出版业
  • 非盈利性组织
  • 公共服务机构
  • 零售业和电商
  • 旅游业和运输业
概况

特色

  • 技术

    深入探索企业技术与卓越工程管理

  • 商业

    及时了解数字领导者的最新业务和行业见解

  • 文化

    分享职业发展心得,以及我们对社会公正和包容性的见解

数字出版物和工具

  • 技术雷达

    对前沿技术提供意见和指引

  • 视野

    服务数字读者的出版物

  • 数字化流畅度模型

    可以将应对不确定性所需的数字能力进行优先级划分的模型

  • 解码器

    业务主管的A-Z技术指南

所有洞见

  • 文章

    助力商业的专业洞见

  • 博客

    ThoughtWorks 全球员工的洞见及观点

  • 书籍

    浏览更多我们的书籍

  • 播客

    分析商业和技术最新趋势的精彩对话

概况
  • 申请流程

    面试准备

  • 毕业生和变换职业者

    正确开启技术生涯

  • 搜索工作

    在您所在的区域寻找正在招聘的岗位

  • 保持联系

    订阅我们的月度新闻简报

概况
  • 会议与活动
  • 多元与包容
  • 新闻
  • 开源
  • 领导层
  • 社会影响力
  • Español
  • Português
  • Deutsch
  • English
ThoughtWorks菜单
  • 关闭   ✕
  • 产品及服务
  • 合作伙伴
  • 洞见
  • 加入我们
  • 关于我们
  • 联系我们
  • 返回
  • 关闭   ✕
  • 概况
  • 工匠精神和科技思维

    采用现代的软件开发方法,更快地交付价值

  • 客户洞察和数字化产品能力

    快速设计、交付及演进优质产品和卓越体验

  • 低摩擦的运营模式

    提升组织的变革响应力

  • 智能驱动的决策机制

    利用数据资产解锁新价值来源

  • 合作伙伴

    利用我们可靠的合作商网络来扩大我们为客户提供的成果

  • 企业级平台战略

    创建与经营战略发展同步的灵活的技术平台

  • 返回
  • 关闭   ✕
  • 概况
  • 汽车企业
  • 清洁技术,能源与公用事业
  • 金融和保险企业
  • 医疗企业
  • 媒体和出版业
  • 非盈利性组织
  • 公共服务机构
  • 零售业和电商
  • 旅游业和运输业
  • 返回
  • 关闭   ✕
  • 概况
  • 特色

  • 技术

    深入探索企业技术与卓越工程管理

  • 商业

    及时了解数字领导者的最新业务和行业见解

  • 文化

    分享职业发展心得,以及我们对社会公正和包容性的见解

  • 数字出版物和工具

  • 技术雷达

    对前沿技术提供意见和指引

  • 视野

    服务数字读者的出版物

  • 数字化流畅度模型

    可以将应对不确定性所需的数字能力进行优先级划分的模型

  • 解码器

    业务主管的A-Z技术指南

  • 所有洞见

  • 文章

    助力商业的专业洞见

  • 博客

    ThoughtWorks 全球员工的洞见及观点

  • 书籍

    浏览更多我们的书籍

  • 播客

    分析商业和技术最新趋势的精彩对话

  • 返回
  • 关闭   ✕
  • 概况
  • 申请流程

    面试准备

  • 毕业生和变换职业者

    正确开启技术生涯

  • 搜索工作

    在您所在的区域寻找正在招聘的岗位

  • 保持联系

    订阅我们的月度新闻简报

  • 返回
  • 关闭   ✕
  • 概况
  • 会议与活动
  • 多元与包容
  • 新闻
  • 开源
  • 领导层
  • 社会影响力
博客
选择主题
查看所有话题关闭
技术 
敏捷项目管理 云 持续交付 数据科学与工程 捍卫网络自由 演进式架构 体验设计 物联网 语言、工具与框架 遗留资产现代化 Machine Learning & Artificial Intelligence 微服务 平台 安全 软件测试 技术策略 
商业 
金融服务 全球医疗 创新 零售行业 转型 
招聘 
职业心得 多元与融合 社会改变 
博客

话题

选择主题
  • 技术
    技术
  • 技术 概观
  • 敏捷项目管理
  • 云
  • 持续交付
  • 数据科学与工程
  • 捍卫网络自由
  • 演进式架构
  • 体验设计
  • 物联网
  • 语言、工具与框架
  • 遗留资产现代化
  • Machine Learning & Artificial Intelligence
  • 微服务
  • 平台
  • 安全
  • 软件测试
  • 技术策略
  • 商业
    商业
  • 商业 概观
  • 金融服务
  • 全球医疗
  • 创新
  • 零售行业
  • 转型
  • 招聘
    招聘
  • 招聘 概观
  • 职业心得
  • 多元与融合
  • 社会改变
敏捷项目管理Bangalore技术

5 Tips for Effective Scope Management

Mangalam Nandakumar Mangalam Nandakumar
Shantala Raman Shantala Raman

Published: Oct 22, 2014

Scope is best defined as the most valuable product/functionality that can be delivered within the constraints of a project or a business. It is not an absolute entity like time or money. It is subject to interpretations, based on our own assumptions.

A common problem that project teams grapple with is when we interpret scope as a number. Teams always identify the set of functionality and come up with their estimates. The release plan and subsequent tracking is all done based on this number. Committing to delivering a certain ‘number’ is not likely to be useful unless all stakeholders understand what ‘value’ that number represents. These five tips will help project and customer teams arrive at a shared understanding of scope, as well as manage scope changes better.

Tip # 1 - Make it visual

A big problem in understanding scope is that while everyone (business, delivery teams) may know what is in scope, nobody really has a clear picture of what is NOT in scope. It is rarely called out. It is usually what customers don't get that makes them sit up and take notice.

The challenge is how to get someone to visualize this.

Every requirement gathering exercise results in process flows, use cases, workflow diagrams, user journeys, feature lists and a broken down list of stories or requirements. The key bit here is how these tie in with each other.

This is where visual representations really help. It takes a lot of effort to put together these visual representations, but the amount of impact they have in helping  customer and delivery teams get a holistic view of what is being created, is definitely worth the effort.

Story Maps - One of the most effective ways of tracking and communicating scope changes are story maps. They give a very good visual representation of the feature workflow and corresponding stories or requirements and of the feature completion status (what’s completed, what’s in progress, what’s yet to be done and what is not planned for a given release).

Story map

Burn-up charts - Another tool that augments story maps is the burn-up chart that gives a view of the projected timeline and cost to complete the given scope.

Burn up chart

Tip # 2 - Communicate planning methodology

This is not directly related to scope management but it is very important to communicate the methodology and assumptions on throughput/velocity that went into project planning, to the customer. Before starting development, the delivery team arrives at the effort estimates and expected throughput. When the team moves into development mode, the actual throughput over the first few weeks will validate the throughput assumptions made during planning and the plan may need to be revised based on the actuals. This is when discussions on scope, time and cost with the customer will start. Educating the customer on assumptions made during planning will make them better prepared to have more meaningful and constructive conversation when such a situation arises.

Tip # 3 - Involve end users during scope definition and development

Delivery teams typically interact with the client product owner to define the scope of a product with very little or no involvement from end users. End users get involved either during user acceptance testing phase when it’s too late or during feature showcases, if you are lucky. Surprise, surprise - quite often, delivery teams realize that end user expectations from the product are quite different from theirs and from those of the client business. This leads to a lot of frustration, last minute scrambling, shortcuts, rework and negotiations before the release, to make the product usable. It helps if the delivery teams, especially the business analysts, work towards getting end users involved as early as possible in the project lifecycle. It also helps to alleviate any threat the client may see from involving end users and reassure them of the time and cost advantages.

Tip # 4 - Put yourself in your client’s shoes

Think from the customer’s perspective while taking minor implementation and functionality decisions with the team. Try this even while suggesting options, alternatives and simpler solutions for feature implementations. This will increase customer’s confidence in your analysis skills, build trust and will have them feeling that their product is in good hands. This will also go a long way in bringing out a high quality product that satisfies both the business and end users alike, with minimum scope churn and timeline slippage. It will pave the way for meaningful and collaborative future conversations on functionality, as well as dialogue-based consultative decisions on scope. Of course, all this requires you to have had the opportunity to spend a good amount of face-time with your client to develop a good understanding of their priorities, concerns and any other aspects which may directly or indirectly impact their decisions.

Tip # 5 - And finally, keep it simple

A good quality for a business analyst to have is the ability to strike a good balance between a working product and a complex product that takes care of all edge case scenarios. In an attempt to build the “perfect” product, analysts sometimes over-engineer the product to handle all possible workflows and scenarios. We have often found it useful to consider the probability of occurrence of a scenario, the criticality of not having a certain functionality, or the impact that a functionality has for the high end user groups before deciding whether it should be handled. This will help bring out a good quality and user-friendly product by making optimum utilization of time and resources.

We hope you find this useful and that it resonates with your idea of how to ease some of the difficulties and avoid common pitfalls while managing scope. We would love to hear from you on other tools and techniques that you used on your projects that made scope management an easy, mutually benefitting and enjoyable exercise for you and for your customer.

This post was co-authored by Mangalam Nandakumar. 

  • 产品及服务
  • 合作伙伴
  • 洞见
  • 加入我们
  • 关于我们
  • 联系我们

WeChat

×
QR code to ThoughtWorks China WeChat subscription account

媒体与第三方机构垂询 | 政策声明 | Modern Slavery statement ThoughtWorks| 辅助功能 | © 2021 ThoughtWorks, Inc.