The Link arrows are now displayed connecting the Predecessor task to its Successors as it should.Without critical path analysis, it can be difficult to identify which tasks need to be completed first in order to meet a project deadline. I removed the 3 from the Summary Task and input that as the Predecessor on those tasks that appeared strange. This is violation number 5 of the article referenced above. The culprit! I see the 3 that has been placed within the Predecessor column on the “Planning” Summary Task (#4). Next, my eyes catch that there are no Predecessors for these tasks of question:Īnd then I see it. Right click on the Gantt Chart and select Layout. Next I thought that somehow the person who developed this template modified the Gantt Chart portion of the Gantt Chart view and changed the default option on how the “Link” arrows are displayed. I inspected the Project Start date only to find it is set to Monday 10/6/14. Then I thought, well maybe the Start date of the project is set to Friday 10/10/14 and task 1 has a constraint. But upon investigation, all tasks were scheduled to start “As Soon As Possible”. I first thought that someone had hard-coded the Start date of these tasks. Here is what happened:Īs I looked at the Gantt Chart portion of the Gantt Chart view, I was curious how a number of the tasks (6,12,13,17,22) were starting nearly a week later than the first task within the schedule.
The individual who produced this schedule violated a number of items found in this article: “ 10 Signs You Don’t Really Know Microsoft Project“.Īs I was in the process of fixing this schedule, I got stumped for just a moment. (Find hundreds of Microsoft Project schedule templates here)Īs I started working with this file, I was extremely disappointed to find many best practices of working with Microsoft Project had not been followed. I elected to open the “Wine Tasting Fundraiser” template found within Microsoft Project 2010. I needed a schedule within Microsoft Project that I could quickly open and work with to provide a demonstration. Here is One Reason Why You Should NOT Assign Predecessors to Summary Tasks within Microsoft Project: Posted on Sunday, October 05 07:59:45 EDT by webadmin MS Project: Why You Should NOT Assign Predecessors to Summary Tasks within MS Project Managing Enterprise Projects: Using Project Online and Microsoft Project Server 2019
0 kommentar(er)
