欢迎来到麦多课文档分享! | 帮助中心 海量文档,免费浏览,给你所需,享你所想!
麦多课文档分享
全部分类
  • 标准规范>
  • 教学课件>
  • 考试资料>
  • 办公文档>
  • 学术论文>
  • 行业资料>
  • 易语言源码>
  • ImageVerifierCode 换一换
    首页 麦多课文档分享 > 资源分类 > PDF文档下载
    分享到微信 分享到微博 分享到QQ空间

    REG NASA-LLIS-1583-2005 Lessons Learned - Project Management Status Reporting.pdf

    • 资源ID:1019206       资源大小:13.39KB        全文页数:2页
    • 资源格式: PDF        下载积分:10000积分
    快捷下载 游客一键下载
    账号登录下载
    微信登录下载
    二维码
    微信扫一扫登录
    下载资源需要10000积分(如需开发票,请勿充值!)
    邮箱/手机:
    温馨提示:
    如需开发票,请勿充值!快捷下载时,用户名和密码都是您填写的邮箱或者手机号,方便查询和重复下载(系统自动生成)。
    如需开发票,请勿充值!如填写123,账号就是123,密码也是123。
    支付方式: 支付宝扫码支付    微信扫码支付   
    验证码:   换一换

    加入VIP,交流精品资源
     
    账号:
    密码:
    验证码:   换一换
      忘记密码?
        
    友情提示
    2、PDF文件下载后,可能会被浏览器默认打开,此种情况可以点击浏览器菜单,保存网页到桌面,就可以正常下载了。
    3、本站不支持迅雷下载,请使用电脑自带的IE浏览器,或者360浏览器、谷歌浏览器下载即可。
    4、本站资源下载后的文档和图纸-无水印,预览文档经过压缩,下载后原文更清晰。
    5、试题试卷类文档,如果标题没有明确说明有答案则都视为没有答案,请知晓。

    REG NASA-LLIS-1583-2005 Lessons Learned - Project Management Status Reporting.pdf

    1、Lessons Learned Entry: 1583Lesson Info:a71 Lesson Number: 1583a71 Lesson Date: 2005-09-13a71 Submitting Organization: LARCa71 Authored by: Robert S. BarnesSubject: Project Management Status Reporting Abstract: In order to effectively manage, information regarding cost, schedule and technical perform

    2、ance, must be communicated to the Project Office. Additionally, the Project Office must be kept informed at all times of scope changes or new requirements. The Space Shuttle Return to Flight Project Office has implemented a disciplined process to document new requirements in order to ensure adequate

    3、 resources (people, facilities and funds) are available to execute the task. Description of Driving Event: End of Year Retreat to review where we have been, where we are, and where we are going. Lesson(s) Learned: a) Deliverables: Show Me Need metrics/Exit Criteria; b) Revisit with Customer when pri

    4、orities/requirements (deliverables) change; c) Technical Task Managers/Leads need to communicate scope changes prior to implementation to the Project Office; d) Technical Task Managers/Leads must have work priced through the Project Office. Project Office is the only entity that communicates resourc

    5、e requirements to the customer; e) How is the Project Office value added to technical execution? Need buy in from technical side that we are value added. NOTE: Resource Unit participants agreed that SSRTFPO is value added; f) Schedule slips are not accompanied by workarounds/mitigation strategies; g

    6、) Get written requirements from the customer PRIOR to writing detailed plans and establishing resource requirements. If customer does not have requirements, write requirements and submit to customer to establish communication with the customer; i) Need to spend according to plan; j) Need disciplined

    7、 process to account for workforce charges. NOTE: Overrun in workforce charges siphons funds from procurement; k) Works best when scheduler works directly with Task Managers. However, when others maintain their own schedule, typically not updated properly. If Provided by IHSNot for ResaleNo reproduct

    8、ion or networking permitted without license from IHS-,-,-Task Manager keeps schedule, must be properly maintained (i.e., updated WHEN items on the critical path change). Recommendation(s): Participants agreed on the need for a Project Quarterly Review to discuss technical content and obtain needed s

    9、ynergism between the work being done. The participants agreed to meet with Task Managers to discuss roles and responsibilities and the need for the Project Office leadership to meet with the customer to clarify these roles and responsibilities and discuss lessons learned. A template for reporting re

    10、quirements was approved and a process for scope changes was discussed. Evidence of Recurrence Control Effectiveness: N/ADocuments Related to Lesson: N/AMission Directorate(s): a71 Exploration Systemsa71 Space OperationsAdditional Key Phrase(s): a71 Configuration Managementa71 Program and Project ManagementAdditional Info: Approval Info: a71 Approval Organization: LARCProvided by IHSNot for ResaleNo reproduction or networking permitted without license from IHS-,-,-


    注意事项

    本文(REG NASA-LLIS-1583-2005 Lessons Learned - Project Management Status Reporting.pdf)为本站会员(registerpick115)主动上传,麦多课文档分享仅提供信息存储空间,仅对用户上传内容的表现方式做保护处理,对上载内容本身不做任何修改或编辑。 若此文所含内容侵犯了您的版权或隐私,请立即通知麦多课文档分享(点击联系客服),我们立即给予删除!




    关于我们 - 网站声明 - 网站地图 - 资源地图 - 友情链接 - 网站客服 - 联系我们

    copyright@ 2008-2019 麦多课文库(www.mydoc123.com)网站版权所有
    备案/许可证编号:苏ICP备17064731号-1 

    收起
    展开