The Short Report Proposal you are working on requires a schedule for the work you propose. Document design and readability play a role in the way you communicate your schedule. Explaining the information in paragraph form makes it harder to read. Consider this example:
At least two weeks before the bowl game, decide on a time, date, and place for your party; and then send out party invitations. Two weeks before the party, focus on preparations that can be finished in advance and then pulled out quickly when game day comes. This preparation includes: Buy and/or make maroon and orange, football-themed party decorations; Find your coolers, buckets, or tubs for drinks, or borrow them from friends; Buy beverages (e.g., beer, Soda or other non-alcoholic drinks, water); Buy disposable plates, bowls, cups, cutlery, and napkins; Gather your serving platters and snack bowls; and Gather or buy bottle openers, if your beer is in bottles. If you can store ice in advance, buy ice, lots of it. The week before game day, plan food for the event, and then arrange for catering, or plan to shop for ingredients and make whatever food can be made in advance yourself. Also plan seating arrangements for the party, borrowing any additional chairs or tables needed, and gathering resources in your home. A few days before game day, do a deep clean of your party location, including cleaning furniture, ice chests, refrigerators, and so forth. The day before the game, spot clean any areas that need it. Put up decorations and set out containers (bowls, platters, ice chests, etc.) so that they are ready to fill. The day of the game, turn your attention to finishing food preparations. Be sure to keep food at a safe temperature before and during the party. If you did not buy ice in advance, buy it an hour before the party begins. Once your guests begin to arrive, relax and enjoy the game.
UGH! You don’t need to read through that oversized paragraph to recognize that the details of the schedule are hard to follow. Document design can improve that information. You can revise the information in many, more readable ways, such as
- a table that lists dates and deliverables or tasks completed.
- a calendar with deliverables and tasked completedwritten on the planned dates.
- a workflow diagram that lists expected dates along with the tasks.
Another popular option is using a Gantt chart, and that is the topic of today’s #InfographicInspiration. The information below from Wrike Project Management Software gives you background and general information on how Gantt charts work.
Note: This infographic needs a text-based transcript. See the Optional Accessibility Transcript Activity for more details.
I had to make a Gantt chart in a freshman engineering course. It was my first time ever making one, and at first, I thought that it was so much extra work for a simple timetable of events. However, I found myself going back to the chart throughout the semester and checking if we were hitting our milestones when we said we would. Gantt charts are unique in the fact that you can measure the speed of your progress and see if you are moving slower or quicker than expected. In the case of our genre analysis, the Gantt chart is very small and limited to what little time we have, but if we were doing this over a full semester, we would be able to add more tasks and spend more time per task.
I also had to do this for my freshman engineering course. I can understand how at first this chart feels excessive, but overall it is a fantastic way to organize ideas and optimize a set of strategies.For my engineering project, my group and I had to create a prototype prosthetic; by utilizing and comparing Grant chats, we chose the optimum design and timetable for the prosthetic. I also love how Grant charts make every team member accountable, as this tool is great for showing the workload and equalizing it among group members.
I am glad to have been introduced to these now. I am a fan of different ways of viewing data, and this is a new way for me. The dependency relationships between tasks is a very useful measure to keep track of. The benefits of them in software development are clear since there are many developer all working on the same project, which explains their resurgence.