The Power of Partnerships: Working Together Versus Working Alone

But you don’t have to do it alone anymore. In a period of 18 months myself and the rest of the team at Elementool, Inc. have conducted extensive research, read dozens of books, run surveys, and received a lot of feedback from our clients about their problems in the way they run their projects.

That helped us to gain an understanding of the challenges that companies face and enabled us to come up with a solution that will help companies have control over their project management process. We want to share our knowledge and expertise in the project management field with you to help you improve your life.

We’ll be covering a lot of ground in this book, guiding you through some very important concepts. But one of the best things about Elementool’s Project Management Formula is that you will start noticing results right away. As you begin adopting the practices I show you, you’ll immediately see improvements in your work and life. That’s because the tools are simple, step-by-step and easy to follow:

Six Sections for Success!

What, exactly, will The Project Management Formula give you? What I am offering you in this book are six sections for success, the last of which – the Formula you’ve been hearing so much about – will provide you with the final five steps, or solutions, that will kick your project management into overdrive!

The six major sections that we will be covering in this book are:

  1. Requirements
  2. The Learning Process
  3. Estimating
  4. Time Management
  5. Scheduling and Planning
  6. The Project Management Formula

The first section, Requirements, breaks down the requirements phase for you. This is a crucial part of project management that gets ignored far too often, so I am going to start you off on the right foot by explaining the “why’s” and “how’s” of good requirements management.

That will be followed by our second section, The Learning Process, which I think you will find truly eye-opening. In that lesson, I reveal some little-known truths about how our minds take in information and process change.

Some people think that, to do their job well, they only have to know the technical aspects of how to perform their tasks. But at Elementool we believe that to get to the next level professionally – to find greater success – you need to be able to think beyond the obvious. It’s important to understand how the mind works so that you can create positive changes with your team members and within yourself.

The third section we’ll cover together, Estimating, is where you learn how to create and provide the best possible estimates for your clients and for your team. I will show you different methods for doing this that you will want to put into action right away. Best of all, they are easy to understand and easy to implement.

The book’s fourth section, which focuses on the extremely crucial skill of Time Management, offers a wealth of information and tips on how you can ensure that your valuable time is used to its best advantage.

In the fifth section, Scheduling and Planning, you’re going to find out practical, easily applicable ways to schedule your projects and keep them on track as you go along. You will also discover in this section that good project management involves managing expectations.

Finally, in the last and most pivotal section of the book, I’m going to teach you The Project Management Formula. This is an easy 5-step system for running projects that we here at Elementool are really excited about, and that you will be able to start using straight away. The five steps of “the Formula” are:

  • Step 1: Define project objectives and collect requirements
  • Step 2: Define the priority of the requirements and features
  • Step 3: Planning iterations
  • Step 4: Running iterations
  • Step 5: Present the product to the client

Project Management is Learned, Not Given

Nobody is just automatically born a great project manager, nor does becoming one happen overnight. Instead, like anything else of value in work or in life, being a great project manager is a skill – or, to be precise, a series of skills – that you have to master over time before those skills become habitual. But many people never quite acquire these skills, because after all change takes time and very few of us have time to spare these days. I understand all this, which is why I’ve done the work for you by assembling the six basic strategies and five simple steps you’ll need to, as the subtitle of this book suggests, “complete projects on time.”

The knowledge is out there; it’s simply a matter of distilling it all down and putting it to use. The challenge isn’t just how, but when? Case in point: there are many books about project management, but who has time to read 400-page books when there is barely any time to finish the things you need to do right now, today?

And even when the project manager is knowledgeable about how to manage projects, usually the team of developers, testers, managers and clients have no knowledge in project management methodologies and that creates miscommunication between the different project stakeholders, leading to frustration and project failure.

Let me give you an example: Tracking the time that team members spend on tasks is very important. It enables the project managers and the team to see how the project is progressing, if there are any delays that need to be addressed, or any changes that need to be made in order to keep the project on track.

The project manager knows that, but the team, who might be a group of excellent programmers who have no knowledge in project management and are not aware of the importance of time tracking, might feel like “big brother” is watching them when team members are asked to report the time they work on assignments.

As a result of not knowing the true reason behind this request, they often object and even refuse to report their time. While it’s human nature to see requests like this as “interference,” this type of basic miscommunication between the project manager and the team leads to arguments, frustration and project delays. In short, project mismanagement.

This is why it is so important for everyone on the team, including developers, testers, managers, and even clients themselves, to be familiar with all the stages that are involved in the project development cycle. And who’s responsible for making them familiar with those stages? That’s right, you; the project manager.

Don’t Just Manage Your Time; Master It!

When it comes to project management, regardless of your position in the company, the size of company or even what industry you’ve been in, time is a mission critical factor that often makes completing projects a challenge.

We’ve all been there: not enough time, no solid schedule, poorly defined goals and objectives, no formal plan, out of control scope creep, miscommunication between people that are involved in the project, etc.

As a result, projects are delayed, time is wasted, clients are angry, your company’s reputation is damaged and you lose customers, people are frustrated and stressed out, team members have to work extra hours to catch up, morale goes down, and employees lose confidence in the company.

If you’ve invested time and money in trick after trick – such as using different project tools, begging and threatening, shouting, motivating team members, holding group discussions, adding more people to the team, and working more hours – but nothing has worked, I would ask you to give this book, and The Project Management Formula it contains, a chance.

Here’s why: You’ve been investing in a host of project management tools and services because you want a better income, a better life for your family, more freedom and independence. But tools alone are useless without solid foundations.

You need strategies for using tools. You’ve been focusing on tools and solving problems instead of focusing on creating strength and power that can be leveraged to avoid problems in the first place. That’s a mindset I hope to change with the Formula I’ll be showing you in this book.

It might help you to think about it this way: let’s say you have the fastest car in the world in your garage. But you don’t know how to drive. The car will be useless to you because you don’t know how to move it, let alone master all the strength, vitality and speed that’s being wasted under the hood. But if you are an excellent driver, even a slow car will be able to get you from one place to another.

In this book I am going to show you how to take charge of your projects and run them in a simple, step-by-step way that will enable you to complete them on time, starting today. This can boost income now and bring you the high-caliber clients that you want to attract. It can also make your company more efficient and competitive and begin refining and spotlighting your brand starting on this very page.

The best part is you don’t need any special background, education, or skills to use this Formula. That said, you do need one special super power to put it into use: action. And not just any action, but aggressive action. Process without action will never produce change. Process without action is simply doing the same things you did yesterday – and the day before – and expecting change.

 Albert Einstein said: “The definition of insanity is doing the same thing over and over again and expecting different results.” Something is missing from that equation; something vital. That something vital is aggressive action.

If you don’t take aggressive action once you’ve seen the path I’ve laid out for you in this book, then I can’t help you. Real Success is for people who take action. Mediocre people follow the herd and wait passively for things to “maybe” change in the future.

You are not like that. How do I know? Because you’re here, with me, reading these words and hoping, ready, for change. I am going to show you how to drive your projects and you’ll be able to use this knowledge with any tool that you currently have.

How to Create Agile Project Schedule

In this clip I’m going to show you how to create an agile project schedule.
As you know, in agile development we take the project and divide it into mini projects called Sprints.




There are many advantages to using the agile method of sprints. A few major ones are:

• Agile development gives you better control over the project – when you run a project, there can be many factors that you need to control. Such as resources, tasks, clients, etc. The more variables there are, the greater the changes are that something will go wrong. Dividing the projects into sprints, gives you better control over the project process since the sprints are shorter and require you to worry about a limited number of factors.
• It makes it easy to keep the project on schedule – if your project is a few months, or a year long, it makes it harder to estimate the project’s schedule. Who can predict what might happen 6 months from now? When you divide the project into short sprints, you only need to schedule one or two sprints at a time. This means that the estimation period is much shorter and more accurate.
• Agile development also helps keeping your clients happy – this is something many people are unaware of. While you work on the project, your clients wait to see results. If the project is long and the clients don’t see results for a period of several months, they start to worry whether things go according to plan. They also sometimes forget why they ordered the project in the first place and might change their mind about it.
When you develop the project in sprints. Each sprint is a mini project. At the end of the sprint, you release it to the clients. This shows them that the project moves forward and keeps them in the loop. They are likely to get less nervous about the schedule and be more committed to it.

OK, now let me show you how you build an agile project schedule.

The first step is to divide the project into workable tasks and submit them to your Issue Tracking account as separate issues.

Then go to Scheduling and click on Edit Schedule to build the project schedule.
The first step is defining a project.
• Click on the Add button and choose the Project option.
• Type the project name.
• The project’s description and start and end date are optional. The system will automatically update the start and end date based on the schedule.
• Click Save.

Now that we have a project, the next step is to define the sprints.
The sprint length is determined based on the project’s length. For example, if the project is 12 months long, the sprints should be between 1-3 months each. On the other hand, the sprints should not be too short. They should be long enough to be considered as a small project.

Click on the + button next to the project’s name.
Choose the option Sprint.
Type the Sprint’s name.
The third step is to add the tasks that should be completed as part of the sprint.
These are the actual work that will be done as part of the sprint.
Click on the + button next to the sprint name and choose the option Issue to add an issue from the Issue Tracking account.
Select the account name and type the issue number. When done click on Save.

Repeat this until all the issues are added to the project.
The final step of building the agile project schedule is to define the estimated time for each issue in the sprint.
Use the Start and End date fields to define the schedule.

As you can see, the schedule of the first sprint is set.
You can repeat these steps to add additional projects and sprints to your project plan.

That’s all for now.

If you already have an Issue Tracking account, you can add Scheduling to your account for only $29.99/month by going to “Control Panel”, clicking on “Edit Accounts”, then clicking on “Manage Account List”, changing the Scheduling package to Premium and clicking on the Update button.

If you still don’t have an Elementool account, click on the ‘Sign Up Now’ button below to open a free trial account.

Do You Have an ETA?

Visibility is one of the main reasons why projects fail. It means that the project manager doesn’t have a full picture of the project’s progress at any given moment.

 

 

 

When you have full visibility, you’re able to stop bottle necks in your project’s progress. This allows you to make changes to the project plan and find ways to solve these bottle necks before it is too late.

I would like to introduce a new feature, The ‘Task Completion Date’ that will allow you to know at any given moment what the status of your project is, and when tasks are going to be completed, by integrating Elementool’s Issue Tracking and Scheduling.

As you remember from our previous clips, you can use Elementool’s Scheduling to define the project’s schedule and the start and end date of each issue that is assigned to the team members.

You can watch the clips called ‘How to Create Project Schedule’ on our blog for more details on how to build the project schedule.

The team members can submit the time that they spend on the tasks in Elementool’s scheduling and this enables you to see the development progress of each task.

I explained how to do that in a recent clip called ‘Track Time Spent on Tasks’.

Now I’m getting to the new feature that we just added:

When a user works on an issue, they can define the estimated completion date on the issue itself, by submitting the completion date in the Priority List section.
The Completion Date is also being displayed on the Scheduling Gantt chart.
When you look at the chart, you can see the issues that are part of the project, their start and end date, and the dark blue bar shows you the actual development progress of each issue. The border of the progress bar represents the estimated completion date of each issue.

By looking at Gantt chart, you can tell within seconds the development progress and the estimated completion date of each issue.
That gives you full visibility of your project development progress and allows you to know if things start to get off track, and make changes to the project to keep it on schedule.

Isn’t that cool?

If you already have an Issue Tracking account, you can add Scheduling to your account for only $29.99/month by going to “Control Panel”, clicking on “Edit Accounts”, then clicking on “Manage Account List”, changing the Scheduling package to Premium and clicking on the Update button.
If you still don’t have an Elementool account, click on the ‘Sign Up Now’ button below to open a free trial account.

 

 

Track Time Spent on Tasks

In this clip I’ll show you how you can use Elementool to track the time that team members spend on issues.
Tracking time enables you to view the progress of the project and make changes to the project plan if needed.
It is also useful for billing in case clients pay you by the hours you spent developing their projects.

To start using this feature, you should have the Issue Tracking and Scheduling services, because time tracking is done using the integration between Issue Tracking and Scheduling.

The first step is to submit the issues to the Issue Tracking account and assigned them to your team members.
I’m guessing you already know how to do that. If not, please see the Issue Tracking User Manual clip for instructions.

The next step is to assign the issues to a project or projects in the Scheduling service.
To do that, please follow these steps:
• Switch to Scheduling.
• Click on Edit Schedule
• Click on the Add button to add a project. You can assign issues to one or more projects.
• Now that the project is defined, click on the Add button to add the issues to the project.

After the issues have been added to the project, the team members can use the Scheduling section on the Issue form to submit the time that they spend on the issues.

To submit the time spent on an issue, please follow these steps:
• Open the issue
• Scroll down to the Scheduling section
• Submit the date and time that you spent working on the issue.
• Click on the Update

If we go back to Scheduling and look at the Gantt chart, we can see the project plan displayed in light blue and the actual time that the team spent on the issues in dark blue. This gives us a quick view of the project progress.

If you still don’t have an Elementool account, click on the ‘Sign Up Now’ button below to open a free trial account.

Effective Time Management and Priority Settings

We want to talk to you about personal time management. This subject is a little bit of a detour from our more specific project management program. But we believe that time management is an issue that affects everyone, and it’s important that you know how to deal with it.



Your ability to maximize your team and your own productivity by maximizing your time and how you use it will greatly influence the results you get. That’s why we’re going to help you improve your time management by sharing some simple strategies that you can implement immediately. They’re easy, and you’re going to start seeing amazing results right away.
The best methods for upping productivity are based on two key objectives: The first objective is to capture all the things that need to be done – now, later, someday, big, little, or in between – into a logical and trusted system that’s outside of your head and off your mind. The second objective is to discipline yourself to make front-end decisions about all the inputs that you let into your life, so that you’ll always have a plan for next actions that can be implemented at any moment.
Most people these days will tell you that they have too much to do and not enough time to get it done. We’ve enhanced our quality of life in so many ways, yet, ironically, we nearly kill ourselves with stress by taking on more work than we have the resources to deal with.
That’s why time management is so important, because it’s really a kind of stress management. Have you ever wondered why you can’t seem to shut down your brain at night when you’re trying to fall asleep? Why are so many thoughts running through your mind all the time? That’s stress. Now let me explain how stress is created. It’s not just the big problems that create stress. All of the little unresolved tasks that we have to deal with sit at the back of our heads, subconsciously creating tension. As soon as you attach a “should” or “need to” to a task, it becomes incomplete. Decisions that you still need to make about whether or not you’re going to do something are already incomplete. If you put your mind’s attention on something that needs to be done, and then don’t complete it because it’s low on the priority list, your mind will have already created an open process that keeps running in the back of your mind, and is going to keep bothering you to complete the task. Worse of all, it takes up your energy and prevents you from having a clear focus on your more important tasks.
It’s kind of like your Windows Task Manager. When you open Task Manager, you see that there are a lot of processes running in the background – processes that you didn’t even know existed. Many of them don’t do anything for days, but there they are consuming your computer memory and causing it to run slowly. But if you shut down the processes that you don’t use, then it frees up the memory and your computer will run faster.
All these open processes create stress. So how do we handle all these processes and how do we minimize stress? The key is to clear the open processes from our mind by having something else managing them.

Usually the reason something is on your mind is because you want the situation to be different than what it currently is. The problem is, you haven’t yet worked out exactly what the intended outcome is, you haven’t decided what the next physical step is, and you haven’t put reminders of the outcome and the action required into a system you trust.
And until you do all that, your brain will refuse to put the matter to rest. You can try to fool the people around you by acting like everything’s okay, but you can’t fool your mind. Only it knows whether or not you’ve come to the conclusions you need. Until you clarify your thoughts, make the decisions, and store the data in a system you can trust, your brain will keep nagging you about the next step and adding to your stress.
You should start by clearing your schedule of all the most urgent projects. Try writing down the project or task that is weighing most heavily on your mind right at this moment. What’s bothering you most, or causing the most distraction? Maybe it’s something that truly interests you or that you’re really passionate about. The point is to identify whatever is consuming you most.
Once you have figured that out, describe your intended successful outcome for this situation in a single, written sentence. What would need to happen for you to be able to check this project off your list? That sentence might be “Handle the situation with Client X” or “Implement a new investment strategy,” or any number of other things. Next, write down the first physical action required to move the situation forward. If you had nothing to do, where would you go right now? What visible action would you take? Does it give you a sense of control and motivation to act? It should. And it’s through this kind of organization and decisive action that you will pursue and reach your goals.

That brings us to the question of how you process this information. First of all, you need to determine what the item is and what you’re going to do about it. For example, maybe you have letters from the bank or the government. Or maybe you received an email from a supervisor about a new company policy.
Ask yourself: Is this item actionable, yes or no? If no action is needed, then you have three options. One, it’s trash – so throw it away. Two, no action is necessary now, but you might need to do something later on, so you mark this item for later reassessment. Three, the item is potentially useful information that you might need later on, so you can classify it as a reference item and file it away.
If it is actionable, then something has to be done. So, ask yourself: What project or outcome have I committed to? And also, what’s the next action required? Determining the next action is a critical step for anything you’ve collected. The next action is the next physical activity that has to be done in order to move the current situation to completion.
Once you’ve decided on the next action, you have three options. Option One: Do it. If that action will take under two minutes, you should do it then and there. Option Two: Delegate it. If you aren’t the right person to do the job, assign it to the appropriate person or entity. Option Three: Defer it. If the action is going to take more than two minutes, and you are in fact the right person to do it, then you can track it for later on a Next Actions list.

The Power of Integration

Hey Allison I have a question for you. Can you give me one reason why I should choose Elementool?

Sure, I can sum it up in one word: Integration.


What do you mean?

I’ll explain: Elementool offers you a full set of tools that helps you to take charge of each stage of the project. It includes:
• Issue Tracking – for assigning tasks to team members and developing them according to priority.
• Scheduling – for managing the project plan and schedule, and for making sure tasks are completed on time.
• Help Desk – for running customer support and making your clients happy.
• Requirements Management – for making sure the project is developed according to what your clients want.
• Test Cases – for making sure everything is tested and no bugs are slipping through the cracks.
Now, let’s assume that you have 20 people on your team and you buy these products from other vendors.
One vendor offers Issue tracking for $20 per month per user.
Another vendor offers Help Desk for $25 per month per user.
A third vendor offers Scheduling for $19 per month per user.
And so on.
You end up with a monthly expense of about $2000 for 20 people.

Wow, that’s a lot of money.

I know! And there’s more. You need to use the different vendor APIs to integrate between the different tools. So your developers have to spend their time working on tool integration instead of working on your projects. And after a while, your tool bundle looks like this.

Oh, boy, that’s not good. So what do you offer? I remember that you mentioned something about integration earlier.

Well, Bob, that’s exactly right. Elementool offers you all the tools as one integrated system. This means that you don’t even need to use any APIs to integrate them. They come together and work together.

That sounds really great. But, wait, how much does it cost?

The entire system, which includes Issue Tracking, Scheduling, Help Desk, Requirements Management and Test Cases, only costs $149.95/month with unlimited users.

Really, unlimited users? Do you mean that I don’t pay per user and can actually have as many users as I want?

Exactly.

So how much would I pay if I had 200 users, or 2,000 users, or… 25,674 users?

$149.95/month.

That’s awesome! How can I start using Elementool?

I’d like to let you try Elementool for 30 days for free. Just click on the Free Trial button below to get started now.


How to Create Project Schedule Part II

Hello!
It’s Allison again, and I want to continue a bit on the subject of how to create a project schedule using Elementool.



With today’s clip you’ll discover the importance of estimating and how you can use it to build a schedule. We’ll also talk about dealing with tasks, and tracking the progress of a project using Elementool. So listen up – you’re going to find out some really useful stuff in this one!

Let’s start by talking about estimates. An estimate is a prediction of how long a project will take to complete and how much it will cost. For more information on ways to create estimates, view Elementool’s Project Management Formula program at www.projectmanagementformula.com, which goes into great detail about various estimation techniques.

When you are planning a project, to ensure that you stay on track to finishing on time, it is vital that you create estimates for each task. Be certain that the people making the estimates are experienced in the type of work that’s being estimated, since this will increase the likelihood of a correct estimate. It can also be helpful to use data from similar past projects to help make estimates for current ones.
Once an iteration begins, you will want to start assigning tasks to team members based on the iteration length, the task priority, and the time required to develop these tasks. As a team, you need to determine what must be accomplished during the iteration, in what order the tasks should be done, and who should do them.

Team members should choose tasks based on their availability, also taking their teammates’ availability into account. The estimates of how long each task should take will make it easier to decide who will be assigned which tasks.

A major factor when it comes to assigning tasks is task priority. The team needs to decide what the highest priority items are – in other words, which features are the most crucial to the success of that iteration. High priority tasks should be assigned first, with the team gradually working its way down to the medium priority features and eventually the lower priority features if there is time. In our Project Management Formula program, we discuss in greater detail priority classifications and how they affect the way a team handles a project.

To create estimates and assign tasks to team members, you should follow these steps:
1. Choose a task on the project task list.
2. Set the task start and end dates.
3. Submit the number of hours that the task should take in the Hours field. This is the total number of hours that all team members will spend on the task.
4. In the Resources column, select the team members that this task is assigned to. The system will automatically evenly split the total number of hours between the team members. You can change the number of hours each person works on the task, in case they don’t spend the same time.
5. Elementool will create the Gantt chart bar representing the task schedule and assign the task to the team member on their personal schedule.
6. As you can see, the task bar is clear and looks empty. When team members submit the time that they spend on the task, the task will start to fill up, representing how much time has been spent.This will enable you to see the development progress of each task. We will have an example of that in our next clip.

That’s it. Building the project schedule is very easy. Anyone can do it.

I’m going to show you a simple way how you can use Elementool Schedule to track the progress of the project. This will allow you to make sure that everything is progressing according to plan, and if it’s not, you’ll be able to see that and make the necessary changes in you project plan to get it back on track.

Although estimates provide a projection of how long tasks are expected to take, it is important that team members submit the actual time that they end up spending on each task, and Elementool can help with this process.

Tracking the time that team members spend on tasks allows project managers and the team to see at what pace the project is progressing. Based on the times being submitted, they can see if there are any delays that need to be addressed, or any changes that must be made in order to keep the project on schedule.

The team submits the time that they spend on each task to the Elementool Scheduling system. They can submit it a few times a day when they finish working on different tasks, or once a day for the entire day.

There are two ways team members can submit tasks:
1. If they use the Issue Tracking to work on issues, they can use the Schedule form on the bottom of the Issue form.
a. Scroll down to the Schedule form.
b. As you can see, this issue has already been included in the project.
c. Submit the date and number of hours that you worked on this issue.
d. You can submit the start and end time and the system will calculate the duration automatically.
e. Or just submit the number of hours that you worked on this issue.
f. When done, click on Update.

2. The second way to submit time is to go to the Schedule application by selecting it from the service dropdown menu at the top of the screen.
a. Click on Add Time.
b. Find the task on the project list.
c. Fill out the date and time and click on Submit button.

The hard part is behind us. Now let’s take a look at the Gantt chart. As you can see, the tasks that were reported are starting to fill up on the chart. This allows you to see how much has been done and how much is still left. In case people work on a task longer than expected, their colored time bar will extend itself outside of the Gantt bar borders. This means that they spent more time than was estimated and probably had less time to work on other tasks. So you might expect delays in the project.

This is all for now. If you want to learn advanced strategies for project scheduling and planning, I recommend that you sign up to Elementool’s Project Management Formula program at: www.projectmanagementformula.com
If you have any questions or comments, please feel free to submit them in the comment section below.

How to Create Project Schedule – Part II

Hi, it’s Allison again.
In this clip I’m going to show you an easy way to build the project schedule based on estimating how long the different tasks should take.



Let’s start by talking about estimates. An estimate is a prediction of how long a project will take to complete and how much it will cost. For more information on ways to create estimates, view Elementool’s Project Management Formula program at www.projectmanagementformula.com, which goes into great detail about various estimation techniques.

When you are planning a project, to ensure that you stay on track to finishing on time, it is vital that you create estimates for each task. Be certain that the people making the estimates are experienced in the type of work that’s being estimated, since this will increase the likelihood of a correct estimate. It can also be helpful to use data from similar past projects to help make estimates for current ones.

Once an iteration begins, you will want to start assigning tasks to team members based on the iteration length, the task priority, and the time required to develop these tasks. As a team, you need to determine what must be accomplished during the iteration, in what order the tasks should be done, and who should do them.

Team members should choose tasks based on their availability, also taking their teammates’ availability into account. The estimates of how long each task should take will make it easier to decide who will be assigned which tasks.

A major factor when it comes to assigning tasks is task priority. The team needs to decide what the highest priority items are – in other words, which features are the most crucial to the success of that iteration. High priority tasks should be assigned first, with the team gradually working its way down to the medium priority features and eventually the lower priority features if there is time. In our Project Management Formula program, we discuss in greater detail priority classifications and how they affect the way a team handles a project.

To create estimates and assign tasks to team members, you should follow these steps:
1. Choose a task on the project task list.
2. Set the task start and end dates.
3. Submit the number of hours that the task should take in the Hours field. This is the total number of hours that all team members will spend on the task.
4. In the Resources column, select the team members that this task is assigned to. The system will automatically evenly split the total number of hours between the team members. You can change the number of hours each person works on the task, in case they don’t spend the same time.
5. Elementool will create the Gantt chart bar representing the task schedule and assign the task to the team member on their personal schedule.
6. As you can see, the task bar is clear and looks empty. When team members submit the time that they spend on the task, the task will start to fill up, representing how much time has been spent.This will enable you to see the development progress of each task. We will have an example of that in our next clip.

That’s it. Building the project schedule is very easy. Anyone can do it.

In our next clip I will show you how team members submit the time that has been spent on each task and how you can track the project progress. I suggest that you check it out.

If you have any questions or comments, please feel free to submit them in the comment section below.