对于指标，我们创建 Web 部件：燃尽图、速度、每次迭代的点数等。 这对于经理或客户来说特别好，可以看到项目所取得的进展，并将帮助他们做出有关功能与发布时间的决策。
为了进行测试，我们有一个简单的 SEND-RECV-ASSERT 语言，它通过抓取 XML 进行自动化测试，每晚运行测试。 我们的主页上有一个绿色/红色的小网页部件，它告诉您测试的统计信息。
这可以通过一些 XML 解析非常简单地完成，因为文档库的后端是 XML。 （我们目前使用一些简单的ActiveX和javascript）
这些指标非常容易设置（只需一些 xml 解析和 html 图表）。 自动化测试需要一些时间来设置测试运行程序，但一旦就位并且足够简单，您甚至可以让客户/经理编写验收测试！ 敏捷！ :)
We actually use Sharepoint for our Agile development and have found it works pretty well for project management/collaboration.
There are 2 things we do which I found particularly useful, metrics tracking and automated testing. We use the document library and infopath to add all of our stories for the project to the site. The infopath form should contain all the information you need for a story: points, estimated time, developer, tester, story tasks, test cases.
For metrics, we create web parts for: burn down charts, velocity, points per iteration, etc. This is especially nice for Managers or customers to see that progress being made on the project and will help them make decisions regarding features vs. release time.
For testing we have a simple SEND-RECV-ASSERT language which runs the tests nightly by scraping the XML for automated tests. The we have a little Green/Red webpart on the main page which tells you the stat of the tests.
This can be done pretty simply with some XML parsing since the backend of the document library is XML. (We currently use some simple ActiveX and javascript)
The metrics are pretty easy to set up (just some xml parsing and html charting). The automated testing takes some time to set up a test runner, but once its in place, and easy enough, you can even have customers/managers write acceptance tests! Agile! :)
If you have SharePoint in house already,along with a user base that is comfortable using it I think it would be fairly easy to get started with using it for SCRUM. I would start with the following:
A site collection to hold 1 scrum site per project
A scrum site should contain:
Document library for the electronic files (add columns for categorization as appropriate)
List of team members
Discussion board
The site can be built from a Wiki site template if its necessary.
Once you get the scrum site "feeling right" save it as a template so its easy to spin up a new one.
This solution may not be designed for SCRUM to the nth degree, but it should be enough to get you started. It seems a lot easier than having the entire team learn a new tool when it sounds like you are undergoing some other pretty radical changes.
你真的应该考虑像 Trello、VersionOne、Rally，甚至Basecamp 为此。 他们都有托管解决方案，并提供免费的社区版本，您可以尝试开始使用。 我对 SharePoint 的经验是它需要大量资源来维护。 如果您使用 Team System 并且有很多为您预先构建的东西，那可能会有所不同 - 尽管我有 Team System 并且仍然选择使用 Wiki 来完成我的项目管理任务。 如果您已经投资了 SharePoint 作为 Intranet 和所有支持人员，那么在这种情况下它也可能是一个可行的解决方案。
SharePoint 不是我首先想到的敏捷开发工具。 YMMV。
You really should consider something like Trello, VersionOne, Rally, or even Basecamp for this. They all have hosted solutions and offer free community versions that you can try out to get started. My experience with SharePoint is that it takes a lot of resources to maintain. If you were using Team System and had a lot of the stuff pre-built for you, that might be different -- although I have Team System and still choose to use a Wiki for my project management tasks. If you already have an investment in SharePoint as an intranet and all of the support staff, then it might be a viable solution in that case, too.
SharePoint is not the tool I would think of first for agile development. YMMV.
You need to try and keep the tool from getting in the way of working. In an ideal world the team will all be sat in a single room with big white boards, however often this is not the case and teams are distributed, or theres a push for some form of backup for the post-its.
I'm a big SharePoint fan and where you have this in house already, your already doing collaboration and team work on the platform. Adding another tool, with unique login's can work but the team need to really want to use them.
I've tried getting SharePoint out of the box to do what I wanted but it fell short. I've tried using Version One (on a number of occasions over many years, with many teams) but I find the tool is too much, there are too many otpions and things that need to be done that it gets in the way - it is a long way from the Whiteboard.
So I decided to develop what I needed for my projects. I needed a simple tool, and using the 37signals (creators of basecamp) approach I needed something with less features than the competition.
21Scrum is a simple scrum tool built on SharePoint that uses the platform, add the things that you need (white board, burndown charts) and leave you to get on with the project.
Perhaps this may be the best option for people who already have and use SharePoint - at least thats the goal.
We've setup a SharePoint workspace with lists for Release/Sprint planning, Product Backlog and Sprint Backlog.
Central element is this Task Board for SharePoint - we can drag & drop stories and tasks - even if we are not at the same location. http://www.youtube.com/watch?v=XW89M0C3N7Q
A burndown report visualises the progress automatically.
AFAIK, Sharepoint is ASP.net with free goodies. It is not designed for agile project management.. so you'd have to roll your own site. IMHO instead of trying to bend the job to the tool you have.. switching to a better tool for the job would be a better option. Check this thread out to see if there is something more lightweight that fits your bill.
Also personally I'm a big fan of not digitizing the development activities.. So I'd use a spreadsheet for the backlog and post its and Big Visible charts. Use a digicam to persist diagram/design discussion snapshots (google whiteboard photo for tools) or for reports. I find that most of the "project management" tools are just excuses for generating instant status updates.. it gets in the way of software development (which is the main goal) and inhibits social interaction way too often.
(disclaimer: absolutely 0 experience with sharepoint.. except what I've read in the last 2 days so may be totally off track)
发布评论
评论（6）
我们实际上使用 Sharepoint 进行敏捷开发，并发现它非常适合项目管理/协作。
我发现我们做了两件事特别有用：指标跟踪和自动化测试。 我们使用文档库和信息路径将项目的所有故事添加到网站。 信息路径表单应包含故事所需的所有信息：点、预计时间、开发人员、测试人员、故事任务、测试用例。
对于指标，我们创建 Web 部件：燃尽图、速度、每次迭代的点数等。
这对于经理或客户来说特别好，可以看到项目所取得的进展，并将帮助他们做出有关功能与发布时间的决策。
为了进行测试，我们有一个简单的 SEND-RECV-ASSERT 语言，它通过抓取 XML 进行自动化测试，每晚运行测试。 我们的主页上有一个绿色/红色的小网页部件，它告诉您测试的统计信息。
这可以通过一些 XML 解析非常简单地完成，因为文档库的后端是 XML。 （我们目前使用一些简单的ActiveX和javascript）
这些指标非常容易设置（只需一些 xml 解析和 html 图表）。 自动化测试需要一些时间来设置测试运行程序，但一旦就位并且足够简单，您甚至可以让客户/经理编写验收测试！ 敏捷！ :)
We actually use Sharepoint for our Agile development and have found it works pretty well for project management/collaboration.
There are 2 things we do which I found particularly useful, metrics tracking and automated testing. We use the document library and infopath to add all of our stories for the project to the site. The infopath form should contain all the information you need for a story: points, estimated time, developer, tester, story tasks, test cases.
For metrics, we create web parts for: burn down charts, velocity, points per iteration, etc.
This is especially nice for Managers or customers to see that progress being made on the project and will help them make decisions regarding features vs. release time.
For testing we have a simple SEND-RECV-ASSERT language which runs the tests nightly by scraping the XML for automated tests. The we have a little Green/Red webpart on the main page which tells you the stat of the tests.
This can be done pretty simply with some XML parsing since the backend of the document library is XML. (We currently use some simple ActiveX and javascript)
The metrics are pretty easy to set up (just some xml parsing and html charting). The automated testing takes some time to set up a test runner, but once its in place, and easy enough, you can even have customers/managers write acceptance tests! Agile! :)
如果您内部已经拥有 SharePoint，并且有一个习惯使用它的用户群，我认为开始将它用于 SCRUM 会相当容易。 我将从以下内容开始：
每个项目包含 1 个 Scrum 站点的站点集
Scrum 站点应包含：
电子文件的文档库（根据需要添加分类列）
团队成员列表
讨论区
如果需要，可以从 Wiki 站点模板构建站点。
一旦您“感觉不错”，就可以将 Scrum 站点保存为模板，以便轻松启动新站点。
该解决方案可能不是专为 SCRUM 设计的，但它应该足以让您入门。 当听起来你正在经历一些其他相当彻底的变化时，这似乎比让整个团队学习新工具容易得多。
我的 0.02 美元
jt
If you have SharePoint in house already,along with a user base that is comfortable using it I think it would be fairly easy to get started with using it for SCRUM. I would start with the following:
A site collection to hold 1 scrum site per project
A scrum site should contain:
Document library for the electronic files (add columns for categorization as appropriate)
List of team members
Discussion board
The site can be built from a Wiki site template if its necessary.
Once you get the scrum site "feeling right" save it as a template so its easy to spin up a new one.
This solution may not be designed for SCRUM to the nth degree, but it should be enough to get you started. It seems a lot easier than having the entire team learn a new tool when it sounds like you are undergoing some other pretty radical changes.
my $0.02
jt
你真的应该考虑像 Trello、VersionOne、Rally，甚至Basecamp 为此。 他们都有托管解决方案，并提供免费的社区版本，您可以尝试开始使用。 我对 SharePoint 的经验是它需要大量资源来维护。 如果您使用 Team System 并且有很多为您预先构建的东西，那可能会有所不同 - 尽管我有 Team System 并且仍然选择使用 Wiki 来完成我的项目管理任务。 如果您已经投资了 SharePoint 作为 Intranet 和所有支持人员，那么在这种情况下它也可能是一个可行的解决方案。
SharePoint 不是我首先想到的敏捷开发工具。 YMMV。
You really should consider something like Trello, VersionOne, Rally, or even Basecamp for this. They all have hosted solutions and offer free community versions that you can try out to get started. My experience with SharePoint is that it takes a lot of resources to maintain. If you were using Team System and had a lot of the stuff pre-built for you, that might be different -- although I have Team System and still choose to use a Wiki for my project management tasks. If you already have an investment in SharePoint as an intranet and all of the support staff, then it might be a viable solution in that case, too.
SharePoint is not the tool I would think of first for agile development. YMMV.
您需要尝试防止该工具妨碍工作。 在理想的情况下，团队将全部坐在一个有大白板的房间里，但通常情况并非如此，团队是分散的，或者需要某种形式的便利贴备份。
我是 SharePoint 的忠实粉丝，您已经在内部拥有了此功能，您已经在该平台上进行协作和团队工作。 添加另一个具有唯一登录名的工具可以工作，但团队需要真正想要使用它们。
我尝试过让 SharePoint 开箱即用来执行我想要的操作，但效果不佳。 我尝试过使用版本一（多年来多次使用，与许多团队合作），但我发现该工具太多了，有太多的选项和需要完成的事情，它会妨碍 - 它距离白板很远。
所以我决定开发我的项目所需的东西。 我需要一个简单的工具，并且使用 37signals（basecamp 的创建者）方法，我需要比竞争对手功能更少的工具。
21Scrum 是一个基于 SharePoint 的简单 Scrum 工具，它使用该平台，添加以下内容您需要的（白板、燃尽图），然后让您继续该项目。
对于已经拥有并使用 SharePoint 的人来说，这可能是最佳选择 - 至少这是目标。
You need to try and keep the tool from getting in the way of working. In an ideal world the team will all be sat in a single room with big white boards, however often this is not the case and teams are distributed, or theres a push for some form of backup for the post-its.
I'm a big SharePoint fan and where you have this in house already, your already doing collaboration and team work on the platform. Adding another tool, with unique login's can work but the team need to really want to use them.
I've tried getting SharePoint out of the box to do what I wanted but it fell short. I've tried using Version One (on a number of occasions over many years, with many teams) but I find the tool is too much, there are too many otpions and things that need to be done that it gets in the way - it is a long way from the Whiteboard.
So I decided to develop what I needed for my projects. I needed a simple tool, and using the 37signals (creators of basecamp) approach I needed something with less features than the competition.
21Scrum is a simple scrum tool built on SharePoint that uses the platform, add the things that you need (white board, burndown charts) and leave you to get on with the project.
Perhaps this may be the best option for people who already have and use SharePoint - at least thats the goal.
我们设置了一个 SharePoint 工作区，其中包含发布/冲刺计划、产品待办事项列表和冲刺待办事项列表。
核心元素是 SharePoint 任务板 - 我们可以拖动并单击任务板。 放下故事和任务 - 即使我们不在同一个位置。
http://www.youtube.com/watch?v=XW89M0C3N7Q
燃尽报告可视化自动进度。
效果很好！
We've setup a SharePoint workspace with lists for Release/Sprint planning, Product Backlog and Sprint Backlog.
Central element is this Task Board for SharePoint - we can drag & drop stories and tasks - even if we are not at the same location.
http://www.youtube.com/watch?v=XW89M0C3N7Q
A burndown report visualises the progress automatically.
Works great!
AFAIK，Sharepoint 是 ASP.net，提供免费的东西。 它不是为敏捷项目管理而设计的..所以你必须推出自己的网站。
恕我直言，不要试图将工作转向你拥有的工具……切换到更好的工具来完成工作将是一个更好的选择。 检查此线程看看是否有更轻量级的东西适合你的账单。
就我个人而言，我非常不喜欢将开发活动数字化。因此，我会使用电子表格来处理积压工作，并发布其和大的可见图表。 使用数码相机保存图表/设计讨论快照（工具的谷歌白板照片）或报告。 我发现大多数“项目管理”工具只是生成即时状态更新的借口......它妨碍了软件开发（这是主要目标）并经常抑制社交互动。
（免责声明：对 sharepoint 的体验绝对是 0。除了我在过去 2 天读过的内容，所以可能完全偏离了轨道）
AFAIK, Sharepoint is ASP.net with free goodies. It is not designed for agile project management.. so you'd have to roll your own site.
IMHO instead of trying to bend the job to the tool you have.. switching to a better tool for the job would be a better option. Check this thread out to see if there is something more lightweight that fits your bill.
Also personally I'm a big fan of not digitizing the development activities.. So I'd use a spreadsheet for the backlog and post its and Big Visible charts. Use a digicam to persist diagram/design discussion snapshots (google whiteboard photo for tools) or for reports. I find that most of the "project management" tools are just excuses for generating instant status updates.. it gets in the way of software development (which is the main goal) and inhibits social interaction way too often.
(disclaimer: absolutely 0 experience with sharepoint.. except what I've read in the last 2 days so may be totally off track)