我们已经成功地使用 MS Project 进行规划，但无法与未安装 MS Project 的客户和同事共享 MS Project 计划。 这让我们想到了在线 Microsoft Project 查看器 - 一项允许查看和共享 MS Project 的服务文件 (.mpp) 在线，除了 MS Project：
希望这会有所帮助。
We've been successfully using MS Project for planning but were missing the ability to share MS Project plans with customers and colleagues who don't have it installed. This led us to the idea of online Microsoft Project viewer - a service that would allow to view and share MS Project files (.mpp) online, apart from MS Project:
There are many better alternatives, at least for software development. One such is embedded in Microsoft Visual Studio Team System. You may also want to check out tools from Rally Software and Version One. The latter are well suited to agile methods, while the former supports both agile and traditional CMM methods.
Well, given the fact that not even the Project team uses Project for Project (Source: Joel Spolsky), I would not want to use it for development.
I track my development tasks in our Bug Tracker, and the Project File just has something like "Planning 1 Week, Development 5 Weeks, QA 3 Weeks, Deployment 1 Week", aka. a VERY broad overview.
As for the BugTracker, FogBugz has this nice Estimate-Tracking that I find quite useful for making schedules, which is for me just another reason to not use Project.
But then again, I am not a Project Manager, so to me, Project is just an unnecessary complex, not really multi-user friendly and somewhat dated-feeling Tool to be used when building Houses, Highways or Space Stations, but not for Software.
We use Primavera on my project. Its supposed to be great although its the only tool I haven't really used for project management so far so I can't really compare it to anything else. Its not that easy to pick up but it can do everything I need (and apparently much more).
My favourite feature is the built in timesheets functionality which means my developers can book their hours to their tasks at the end of the week meaning that I don't need to constantly bug them about how they are progressing against their plans.
personally i dont believe ms project is good for software dev (i have used it, im not bashing it to be a purist)
its great if you are building a house or something which doesnt have such uncontrollable variables (e.g. how many bugs will you have? how long will bugs take to fix? how much feature-creep will there be?)
i like to keep my schedules very simple so more people can understand them, hence why i just use a google spreadsheet
如果您使用的是 Microsoft 堆栈，Team Foundation Server 是一个良好的项目管理解决方案。 它与 Project 集成以进行调度，还提供了源代码控制、工作项（任务/缺陷）跟踪和文档管理（通过共享点）的基本功能。2008 版本已经非常成熟，2010 版本看起来非常有前途，尤其是在需求规范和可追溯性领域。
Project is not good for managing development at all. I find it marginally useful for scheduling / work breakdown.
If you're on a Microsoft stack, Team Foundation Server is a good project management solution. It integrates with Project for scheduling and also provides the essentials of source control, work item (task / defect) tracking, and document management (via sharepoint.) The 2008 version has matured nicely, and the 2010 version looks very promising, especially in the area of requirements specification and traceability.
You can replicate the TFS features with a stack of open source and/or less expensive off-the-shelf software, but it is more work to integrate. It's debatable which is more flexible and easier to maintain once set up.
The following are required, regardless of platform:
Bug tracking
Work item / story / progress tracking of some kind (may be managed by above)
Collective team discussion (may be managed by above - discussion on work items, like FogBugz for example)
Source control (anything but SourceSafe)
Continuous build integration that runs unit tests
Instant messaging (OpenFire works great if your network blocks external services)
Document library
Farm of virtualized test machines (especially useful for install/upgrade testing)
I tend to use MSProject for capacity planning - a nice big broad brush of who could do what over a period, at a level of abstraction that makes it easy to rejig plans. For day to day tracking of the real work, I use Fogbugz. I think of it as MSProject/Gantty stuff for the strategic planning, and Fogbugz for the tactical management and planning.
正如艾森豪威尔所说：“在备战的过程中我一直发现计划是没有用的，但计划却是不可或缺的。” MS Project 是一个有用的规划工具。
Depends on the process you're using - if it's a waterfall like process, or there's a lot of non-software parts of the project (infrasstructure, manufacturing, marketing etc) then Project's OK for the overall task management - it's certainly competitive with other similar tools.
I don't think any of the "project management" tools (tasks, WBS, gannt charts etc) are much good at the management of the detailed tasks that happen when you're into the main software development phase - I usually end up in Excel for the projects I'm involved in.
And of course, there is much more to the successful management of a non-trivial software project than the bit that can be managed with a tool like Project. It doesn't help much with managing the requirements, issues, defects, meetings, test development etc - but then it's not supposed to.
Because of these limitations, I find I usually get most value out of Project in the planning phase - working out the task breakdown, what needs to be done, and roughly what needs to happen in what order.
As Eisenhower put it: "In preparing for battle I have always found that plans are useless, but planning is indispensable." MS Project is a useful tool for planning.
发布评论
评论（11）
如果还需要一个免费且开放的 Project 替代方案，您可以使用 OpenProj：http://openproj.org/openproj
If also need a free and open alternative to Project, you have OpenProj: http://openproj.org/openproj
我们在这里使用目标进程。 它有一些“主义”，但总的来说是一个很好的敏捷项目管理工具
We use Target Process here. It has a few "-isms", but overall is a good agile project management tool
我们已经成功地使用 MS Project 进行规划，但无法与未安装 MS Project 的客户和同事共享 MS Project 计划。 这让我们想到了在线 Microsoft Project 查看器 - 一项允许查看和共享 MS Project 的服务文件 (.mpp) 在线，除了 MS Project：
希望这会有所帮助。
We've been successfully using MS Project for planning but were missing the ability to share MS Project plans with customers and colleagues who don't have it installed. This led us to the idea of online Microsoft Project viewer - a service that would allow to view and share MS Project files (.mpp) online, apart from MS Project:
Hope this helps.
我们在工作场所使用 Acunote，但我们遵循敏捷/Scrum 方法。
什么构成“最好的工具”取决于很多因素。 你如何运行你的项目，谁将使用它们，等等。
We use Acunote at my work place, but we follow a Agile/Scrum methodology.
What constitutes the "best tool" depends on many things. How you run your projects, who will be using them, etc.
有很多更好的选择，至少对于软件开发来说是这样。 其中之一嵌入在 Microsoft Visual Studio Team System 中。 您可能还想查看 Rally Software 和 版本一。 后者非常适合敏捷方法，而前者则支持敏捷方法和传统 CMM 方法。
There are many better alternatives, at least for software development. One such is embedded in Microsoft Visual Studio Team System. You may also want to check out tools from Rally Software and Version One. The latter are well suited to agile methods, while the former supports both agile and traditional CMM methods.
好吧，考虑到甚至项目团队都没有使用 Project for Project（来源：Joel Spolsky），我不想将其用于开发。
我在 Bug Tracker 中跟踪我的开发任务，项目文件中只有“规划 1 周，开发 5 周，QA 3 周，部署 1 周”之类的内容。 非常广泛的概述。
至于 BugTracker，FogBugz 有一个很好的估计跟踪功能，我发现它对于制定计划非常有用，这对我来说是不使用 Project 的另一个原因。
但话又说回来，我不是项目经理，所以对我来说，Project 只是一个不必要的复杂工具，不是真正的多用户友好型，而且有些过时的感觉，适合在建造房屋、高速公路或空间站时使用，但不适用于软件。
Well, given the fact that not even the Project team uses Project for Project (Source: Joel Spolsky), I would not want to use it for development.
I track my development tasks in our Bug Tracker, and the Project File just has something like "Planning 1 Week, Development 5 Weeks, QA 3 Weeks, Deployment 1 Week", aka. a VERY broad overview.
As for the BugTracker, FogBugz has this nice Estimate-Tracking that I find quite useful for making schedules, which is for me just another reason to not use Project.
But then again, I am not a Project Manager, so to me, Project is just an unnecessary complex, not really multi-user friendly and somewhat dated-feeling Tool to be used when building Houses, Highways or Space Stations, but not for Software.
我们在我的项目中使用 Primavera 。 它应该很棒，尽管它是我迄今为止唯一没有真正用于项目管理的工具，所以我无法将它与其他任何工具进行比较。 它并不容易上手，但它可以完成我需要的一切（显然还有更多）。
我最喜欢的功能是内置的时间表功能，这意味着我的开发人员可以在周末预订他们的任务时间，这意味着我不需要不断地向他们询问他们的计划进展情况。
We use Primavera on my project. Its supposed to be great although its the only tool I haven't really used for project management so far so I can't really compare it to anything else. Its not that easy to pick up but it can do everything I need (and apparently much more).
My favourite feature is the built in timesheets functionality which means my developers can book their hours to their tasks at the end of the week meaning that I don't need to constantly bug them about how they are progressing against their plans.
个人我不相信MS项目对软件开发有好处（我已经使用过它，我并不是抨击它是一个纯粹主义者）
如果你正在建造一座房子或一些没有这种不可控变量的东西，那么它很棒（例如，你会有多少错误？错误需要多长时间才能修复？会有多少功能蔓延？）
我喜欢让我的日程表非常简单，以便更多的人可以理解它们，因此为什么我只使用谷歌电子
表格我使用的结构在这里进一步描述：使用 Google 电子表格的项目时间表< /a>
希望这有帮助
--LM
personally i dont believe ms project is good for software dev (i have used it, im not bashing it to be a purist)
its great if you are building a house or something which doesnt have such uncontrollable variables (e.g. how many bugs will you have? how long will bugs take to fix? how much feature-creep will there be?)
i like to keep my schedules very simple so more people can understand them, hence why i just use a google spreadsheet
the structure i use is described further here: Project Schedules with Google Spreadsheets
hope this helps
--LM
项目根本不利于管理开发。 我发现它对于安排/工作分解来说有点用处。
如果您使用的是 Microsoft 堆栈，Team Foundation Server 是一个良好的项目管理解决方案。 它与 Project 集成以进行调度，还提供了源代码控制、工作项（任务/缺陷）跟踪和文档管理（通过共享点）的基本功能。2008 版本已经非常成熟，2010 版本看起来非常有前途，尤其是在需求规范和可追溯性领域。
您可以使用一堆开源和/或更便宜的现成软件来复制 TFS 功能，但集成起来需要更多工作。 设置后哪个更灵活且更容易维护是有争议的。
无论平台如何，都需要以下内容：
Project is not good for managing development at all. I find it marginally useful for scheduling / work breakdown.
If you're on a Microsoft stack, Team Foundation Server is a good project management solution. It integrates with Project for scheduling and also provides the essentials of source control, work item (task / defect) tracking, and document management (via sharepoint.) The 2008 version has matured nicely, and the 2010 version looks very promising, especially in the area of requirements specification and traceability.
You can replicate the TFS features with a stack of open source and/or less expensive off-the-shelf software, but it is more work to integrate. It's debatable which is more flexible and easier to maintain once set up.
The following are required, regardless of platform:
我倾向于使用 MSProject 进行容量规划 - 一个很好的大范围的刷子，在一个抽象的水平上，在一段时间内谁可以做什么，可以很容易地重新调整计划。 为了日常跟踪实际工作，我使用 Fogbugz。 我认为它是 MSProject/Gantty 的战略规划工具，Fogbugz 的战术管理和规划工具。
I tend to use MSProject for capacity planning - a nice big broad brush of who could do what over a period, at a level of abstraction that makes it easy to rejig plans. For day to day tracking of the real work, I use Fogbugz. I think of it as MSProject/Gantty stuff for the strategic planning, and Fogbugz for the tactical management and planning.
取决于您使用的流程 - 如果它是类似瀑布的流程，或者项目中有很多非软件部分（基础设施、制造、营销等），那么 Project 就可以进行整体任务管理 - 它肯定与其他项目具有竞争力类似的工具。
我认为任何“项目管理”工具（任务、WBS、甘特图等）都不太擅长管理进入主要软件开发阶段时发生的详细任务 - 我通常会以Excel 适合我参与的项目。
当然，成功管理一个重要的软件项目比使用 Project 这样的工具可以管理的内容要多得多。 它对于管理需求、问题、缺陷、会议、测试开发等没有多大帮助——但它不应该有这样的帮助。
由于这些限制，我发现我通常在计划阶段从 Project 中获得最大价值 - 制定任务分解、需要做什么以及大致需要以什么顺序发生。
正如艾森豪威尔所说：“在备战的过程中我一直发现计划是没有用的，但计划却是不可或缺的。” MS Project 是一个有用的规划工具。
Depends on the process you're using - if it's a waterfall like process, or there's a lot of non-software parts of the project (infrasstructure, manufacturing, marketing etc) then Project's OK for the overall task management - it's certainly competitive with other similar tools.
I don't think any of the "project management" tools (tasks, WBS, gannt charts etc) are much good at the management of the detailed tasks that happen when you're into the main software development phase - I usually end up in Excel for the projects I'm involved in.
And of course, there is much more to the successful management of a non-trivial software project than the bit that can be managed with a tool like Project. It doesn't help much with managing the requirements, issues, defects, meetings, test development etc - but then it's not supposed to.
Because of these limitations, I find I usually get most value out of Project in the planning phase - working out the task breakdown, what needs to be done, and roughly what needs to happen in what order.
As Eisenhower put it: "In preparing for battle I have always found that plans are useless, but planning is indispensable." MS Project is a useful tool for planning.