PROJ 584 Week 3 Discussion; Managing Project Scope and Schedule Management

Week 3: Managing Project Scope and Schedule Management Discussion The topic below pertains to the materials covered in the weekly lesson. In addition to a text description, you may add a screen capture, a matrix, or other creative image that supports your ideas. You are to submit three quality posts over 3 different days, with the first post on or before Wednesday for each graded discussion topic. Use references from your textbooks. After reading Chapter 6: Project Schedule Management in the textbook Information Technology Project Management (2019) by Kathy Schwalbe, review the importance of schedule management and then discuss the following tools and explain why they are important. Network diagrams Activity sequencing Estimating activities Critical path Also, explain the Software Development Life Cycle (SDLC) that you are using on your Course Project and state specifically how your Course Project may be impacted if the items above are not used. View Instructor posts View My Posts Search entries or author Filter replies by unreadUnread Collapse replies Expand replies SubscribedReplyReply to Week 3: Managing Project Scope and Schedule Management DiscussionCollapse SubdiscussionEmre OzmenManage Discussion EntryHello Folks, I wish you a great week. Here is my perspective: Emre OzmenMay 17, 2021Local: May 17 at 10:30am<br>Course: May 17 at 12:30pm • You may remember that you will return your project charter this week. There is a template proposal of mine that I've uploaded in my Files, it's from the New York University. It primarily aims to give high-level (1 or 2 pages) information about your project, so you can be authorized accordingly. Scope statement is what-we-do, it is an extended version of a project charter. It usually 3-to-10 pages, in other words, it's more than a WBS. The reason that it is very important is the fact that you manage your invoicing per your scope statement, a.k.a. acceptance criteria. Therefore, anything you miss here or vague scope statements with ambiguities might create significant risks. Sequencing makes the heart of our schedule, since it's not just about when-we-do, it's also the phase that we define our dependencies and failing with dependencies are not always tolerable per re-works, damage might be very significant. Critical path is crucial because of two reasons, first you'll know what will make you late, a.k.a. tasks on your critical path, second you'll also know where you have some flexibility, a.k.a. non-critical tasks, so you can redistribute your resources if there is a need. The vast majority of our resources are "Work", i.e. manpower, cost estimations heavily depend on duration estimations. Lastly, knowing that the vast majority here sticks with deployment projects, mostly, I'd like to start with the simpliest SDLC form first: Analyze-Deploy-Test What would be your (I would not go for more than 5 phases here) preference? Edited by Emre Ozmen on May 17 at 2:41pm Reply Reply to Comment • Collapse SubdiscussionMichael WithersMichael WithersMay 17, 2021Local: May 17 at 2:30pm<br>Course: May 17 at 4:30pm Manage Discussion EntryHi Everyone, The tools used in schedule management are important as they offer a