The assignment
The team Kreaz is expected to produce a Gantt chart and to keep it up to date for use in planning your project. We are start using GanttProject for produce our charts. With this tool we can simply separate task in category, establishing milestones, work progress and relationships between them.
(Sorry my english, but I'm on language rodaje!)
We follow these guidelines in creating our chart:
- Use weeks as the time unit
- Include the Mid-project review, Design Show, and Final report due as milestones. Have up to four additional milestones, no more.
- Show more detail on design tasks, less detail on reports/documentation/presentation tasks. Should have about 3/4 design tasks, 1/4 documentation/presentation related tasks.
- Getting parts can take 2 weeks or more, depending on the part. If your company is building parts for your prototype, getting your part scheduled can take a long time. Build these delays into your planning chart.
- Review and update Gantt chart every 14 days, more often if needed.
Project Planning for Software Development
A Project is a set of activities which ends with specific accomplishment and which has
- Non-routine tasks
- Distinct start/finish dates, and
- Resource constraints (time/money/people/equipment)
"Tasks" are activities which must be completed to acheive project goal. Break the project into tasks and subtasks. Tasks have start and end points, are short relative to the project and are significant (not "going to library", but rather, "search literature"). Use verb-noun form for naming tasks, e.g. "create drawings" or "build prototype". Use action verbs such as "create", "define" and "gather" rather than "will be made". Each task has a duration. Very difficult to estimate durations accurately. Doubling your best guess usually works well.
"Milestones" (Hitos) are important checkpoints or interim goals for a project. Can be used to catch scheduling problems early. Name by noun-verb form, e.g. "prototype complete", commonly used for Software.
Your plan will evolve so be flexible and update on a regular basis. It also helps to identify risk areas for project, for example, things you don't know how to do but will have to learn. These are risky because you may not have a good sense for how long the task will take. Or, you may not know how long it will take to receive components you purchased for a project.
there are some notes that I dont have to forget.
