敏捷开发的项目规划

罗伯特•波达尔

你好,

我想了解一下您是如何为敏捷软件开发准备项目计划的。我明白，首先需要创建产品待办事项列表，其中包含发布所需的ob欧宝娱乐app手机下载功能/bug/增强列表，然后在Spring计划期间，与PO讨论并理解票据，然后完成故事指出。在他们被团队“拉”进Sprint之后。

我的问题:

1.如何在项目开始时准备项目计划，因为管理层想知道可交付成果的发布日期。

2.随着sprint的开发，项目计划也随之更新。这意味着该计划是为第一次Sprint准备的，一旦完成，那么在第二次Sprint计划期间，项目计划将被更新。这种理解正确吗?

3.如果第2点是正确的，那么就没有任何办法预先指出发布日期。我假设没有任何基线v/s实际的概念(就像在瀑布开发中那样)。

谢谢

罗伯特。

贝琪绿色

你好,罗伯特。

你说的“项目计划”是指时间表吗?

罗伯特•波达尔

嗨贝琪

是的，我说的项目计划是指进度计划。

贝琪绿色

对于我们这些习惯了瀑布式方法的人(我)来说，这就是敏捷方法变得棘手的地方。

最新版的PMBOK描述了两种方法:

• 有待办事项的迭代调度——这听起来像是你正在尝试的
  • 需求记录在用户存储库中，在开发之前对其进行优先级排序
  • 功能是在sprint中创建的
  • 理想情况下，其中一些可交付成果可以在您进行的过程中完成并交给客户，而不是一次完成所有工作
  • 你的日程安排将与开发团队一起决定每个sprint的内容以及每个sprint需要多长时间才能完成。在此基础上，你可以制定出某种时间表。
  • 所以，它更像是，“嘿，我们每三周发布一次。以下是我们计划在每个版本中添加的内容。”
  • 时间表将是迭代的。它只是不会像瀑布环境中的进度管理那样工作。
• 按需调度，使用看板，它看起来很像Smartsheet中的卡片视图。
  • 当资源可用时，工作被放入backlog或队列中欧宝体育app官方888
  • 您可能会得到一个估计，因为每个排队交付的优先级
  • 这对于增量更改更有效
  • 这就像是，“这里有一张需要做的事情的清单。好消息是，Sarah可以创建这个功能，两周内就能完成。”

我很想知道其他人是如何在敏捷环境中处理日程管理的。虽然我对这个想法持开放态度，但这种方法还没有取得多大成功。

——贝西

罗伯特•波达尔

嗨,贝琪,

是的，你说得对。在瀑布式开发的背景下，很难制定项目时间表/计划。我一直在看一些文章，视频，这是我所理解的;但我不能百分之百确定这是否是安排日程的方式。

1.该版本的票证在产品待办事项列表中。ob欧宝娱乐app手机下载

2.在Sprint计划期间，对门票进行筛选和估算。团队决定将进入Sprint的票据，并确定Sprint持续时间。

3.在这一点上，项目进度表/计划将显示Sprnt1中团队已经同意的票证列表。

4.一旦Sprint完成，剩余的票据将转移到Backlog /下一个Sprint。再一次，下一组票被拿起来，擦洗和估计。时间表/计划相应更新。

如果这是准备时间表的“正确”方式/方法，那么在敏捷中没有任何基线概念。如果没有，那么项目经理就无法跟踪计划的实际情况。

如果是这样的话，那么如果PO指定一个他想要发布的日期，并且团队根据该日期对票证进行工作，是否可以?随着团队的发展，为了满足发布日期，可能需要放弃一些非关键的票据。项目进度表/计划将不是一个参考工具，而是跨多少个sprint完成实际工作的工具。

对于未来类似的项目，我们使用项目进度表/计划来指示团队花了多少个月来发布一个版本。

我也很想知道Smartsheet社区和Smartsheet团队是如何准备各自的项目时间表/计划的。希望能得到一些帮助…

吉卜兰·艾哈迈德·谢赫

Hi Betsy, <\/p>\n

Yes, you are right. Coming from a waterfall background, it is very difficult to put a project schedule\/plan in place. I have been going through some articles, videos and this is what i have understood; but i am not 100% sure if this is how scheduling needs to be done. <\/p>\n

1. Tickets for the release are into the product backlog. <\/p>\n

2. During the Sprint planning, the tickets are scrubbed and estimated. The team decides on the tickets that will go into the Sprint and the Sprint duration is identified. <\/p>\n

3. At this point, the project schedule \/ plan will indicate the list of tickets that have agreed by the team in Sprnt1. <\/p>\n

4. Once the Sprint is completed, the residue tickets will move to the Backlog \/ next Sprint. Once again the next set of tickets are taken up and scrubbed & estimated. The schedule \/ plan is updated accordingly. <\/p>\n

If this the \"right\" way \/ method to prepare the schedule, then one thing is that there isn't any Baseline concept in Agile. If there isn't then the project manager cannot track the plan v\/s actual. <\/p>\n

If this is the case, then is it ok if the PO indicates a date when he would like a release and the team works on the tickets to meet that date? As the team goes along, some non critical tickets may need to be dropped in order to meet the release date. The project schedule \/ plan will not be a reference tool, but a tool for the actual work done, across how many Sprints. <\/p>\n

For future similar project, we use the project schedule \/ plan to indicate how many months it has taken the team to make a release. <\/p>\n

I too am interested to know how Smartsheet community and the Smartsheet team has been preparing their respective project schedule \/ plans.. Hope to get some help.. <\/p>","bodyRaw":"

Hi Betsy, <\/p>\n\n

Yes, you are right. Coming from a waterfall background, it is very difficult to put a project schedule\/plan in place. I have been going through some articles, videos and this is what i have understood; but i am not 100% sure if this is how scheduling needs to be done. <\/p>\n\n

1. Tickets for the release are into the product backlog. <\/p>\n\n

2. During the Sprint planning, the tickets are scrubbed and estimated. The team decides on the tickets that will go into the Sprint and the Sprint duration is identified. <\/p>\n\n

3. At this point, the project schedule \/ plan will indicate the list of tickets that have agreed by the team in Sprnt1. <\/p>\n\n

4. Once the Sprint is completed, the residue tickets will move to the Backlog \/ next Sprint. Once again the next set of tickets are taken up and scrubbed & estimated. The schedule \/ plan is updated accordingly. <\/p>\n\n

If this the \"right\" way \/ method to prepare the schedule, then one thing is that there isn't any Baseline concept in Agile. If there isn't then the project manager cannot track the plan v\/s actual. <\/p>\n\n

If this is the case, then is it ok if the PO indicates a date when he would like a release and the team works on the tickets to meet that date? As the team goes along, some non critical tickets may need to be dropped in order to meet the release date. The project schedule \/ plan will not be a reference tool, but a tool for the actual work done, across how many Sprints. <\/p>\n\n

For future similar project, we use the project schedule \/ plan to indicate how many months it has taken the team to make a release. <\/p>\n\n

I too am interested to know how Smartsheet community and the Smartsheet team has been preparing their respective project schedule \/ plans.. Hope to get some help.. <\/p>","format":"html","dateInserted":"2018-08-16T02:54:04+00:00","insertUser":{"userID":5523,"name":"Robert Poddar","url":"https:\/\/community.smartsheet.com\/profile\/Robert%20Poddar","photoUrl":"https:\/\/us.v-cdn.net\/6031209\/uploads\/defaultavatar\/nWRMFRX6I99I6.jpg","dateLastActive":"2019-02-28T07:58:01+00:00","banned":0,"punished":0,"private":false,"label":"✭"},"displayOptions":{"showUserLabel":false,"showCompactUserInfo":true,"showDiscussionLink":false,"showPostLink":false,"showCategoryLink":false,"renderFullContent":false,"expandByDefault":false},"url":"https:\/\/community.smartsheet.com\/discussion\/comment\/95286#Comment_95286","embedType":"quote"}"> https://community.smartsheet.com/discussion/comment/95286#Comment_95286

很神奇的。给出合理的解释。