Product Requirements

Every project begins with requirements.

Although this step is very important, it is often neglected by companies because people see it as a “waste of time.” Both the developers and clients want to get right to writing the software code because then they feel that the project is progressing, but the result of poor requirements is having to make changes to the system later in the project and sometimes even starting the project all over. And this is a waste or precious time, money and resources.

Not defining the project’s requirements and business objectives is considered to be the number one reasons why projects fail.

Clearly, we must learn the requirements before starting the project. In other words, what does the client/customer require? That is the original question upon which the rest of the project hinges. If you don’t know what the customer really wants, then you’ll be managing the wrong project or, just as bad, managing the right project in the wrong manner.

        Many companies trust the client to know what he wants. Unfortunately, clients generally only know what they “think” they want and rarely work through to the end result. One of the most important aspects of project management is getting to the requirements first so that the rest of the project goes smoothly.

       Careful planning, questioning and soliciting are critical to the requirements process, and that is the groundwork we’ll be laying in this first, critical section.

Projects aren’t just comprised of a beginning, a middle and an end but dozens, even hundreds, of working parts. The more “parts” you’re forced to work with, the more challenging the project can be. But if you can nail the requirements before even getting started on the project itself, the challenges you’ll face later will be both less problematic and less frequent.

Posted in Uncategorized | Tagged , , , , , | Comments Off on Product Requirements

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
Posted in Uncategorized | Tagged , , , , , , , , , | Comments Off on The Power of Partnerships: Working Together Versus Working Alone

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.

Posted in Uncategorized | Tagged , , , , | Comments Off on Project Management is Learned, Not Given

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.

Posted in Uncategorized | Tagged , , , , | Comments Off on Don’t Just Manage Your Time; Master It!

Instant Messaging

Instant messaging has become common in our daily routine. So we have decided to offer it as part of Elementool to help you improve your communication with your team members. Especially if they are located someplace else.


To start a new conversation using the Instant Messenger, please follow these steps:

• Click on the ‘number of users’ online link at the top of the page to display who is currently logged in to the account.
• Click on the name of the user to start an Instant Message session.
• The Messenger window will be displayed on your screen.
• Type your message and click on the keyboard Enter button to send it.

When someone starts a new conversation with you, you will see a red flag next to the ‘number of users’ link.
Follow these steps to join an instant message session:

• Click on the ‘number of users’ online link at the top of the page.
• The person who sent you the message will be marked on the user list.
• Click on the user’s name to open the messenger window.
• Type your reply in the text box and click on the keyboard Enter button to send it.

As you can see, Instant Messaging is easy and can make the communication with your team faster and more efficient.

Posted in Uncategorized | Tagged , , , , , , , , , , , | Leave a comment

How to Edit Your Customer List

In this clip I’d like to introduce a new feature in our Help Desk software called ‘Customer List’.
As you are probably guessing, the Customer List enables you to define your customer contact details in your Help Desk account.

This way you can store and display on the Help Desk ticket form the customer name, email address, phone number and other contact details. So you can easily contact the client about the specific Help Desk ticket if needed.

The first step is setting up the client list.
To setup the client list, please follow these steps:
1. Login as an administrator.
2. Click on Control Panel.
3. Click on Edit Customer List.
4. Use the Add New section to add a new customer to the list.
5. You can also edit existing customers by clicking on the Edit button on the right.

The next step is to choose the customer name on your Help Desk ticket form.
On the ticket form, the customer name field displays a dropdown list of the customers. When choosing a name from the list, the customer details are automatically updated.

Very simple.

We plan to add additional options to the customer list feature in the upcoming weeks. Stayed tool.

If you already have an Issue Tracking account, you can add Help Desk 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 Help Desk 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.

Posted in Uncategorized | Tagged , , | Leave a comment

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.

Posted in Uncategorized | Tagged , , , , , , , , , | Leave a comment

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.

Posted in Uncategorized | Tagged , , , , , , , , , , | Leave a comment

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.

Posted in Uncategorized | Tagged , , , , , , , , , , , , | Leave a comment

How to Send Daily Reports

Hi, it’s Allison again.
Today I would like to present two new features that we added to the reporting section:

• The option to define the view type of the Quick Reports.
• The option to automatically send a daily report by email.

The reports offer 5 view types:
• Normal – this is the standard report type that is display on your browser.
• Dynamic – The Dynamic view type enables you to make changes to the issues directly on the report. This allows you to update multiple issues in a single update instead of opening each issue separately.
• Print View – this is a printer friendly view of the report, that is useful in case you wish to print the report.
• Excel CSV and Excel HTML – these two view types enable you to export the report to an Excel file. Each offers a different Excel formatting option and you can choose the one that suits you the most.

We added an option to define the view type of each Quick Report. It saves you the trouble of defining how you would like the report to look like when running it.

Please follow these steps to change the view type of an existing report:
• Select the report from the Quick Report list.
• Click on Edit Selected Report.
• The Quick Report setup window will open.
• Click on the Step 3 button and the on the Step 4 button to go to the Step 4 page.
• On this page define the View Type and click on Save.

The Send Daily Report option enables you to send reports on a daily basis to other Elementool users or to external people who don’t use Elementool.
It is an easy way to send updates about tasks and issues that you have in your account.

For example: every morning you can send a report of all the open issues in your account, to inform people of the tasks that need to be taken care of.

To setup an automatic daily report, please follow these simple steps:
1. Go to the report page by clicking on Issue Report.
2. Select a report from the Quick Report list.
3. Click on Send Selected Report.
4. Define the recipients by selecting Elementool users or by typing email addresses of external people.
5. Check off the ‘Send report automatically daily’ check box.
6. Select the time when you would like to report to be sent daily.
7. Click on Send.

Very easy.

We plan to release more new features in the near future.
Stay tuned!

Posted in Uncategorized | Tagged , , , , , , , | Leave a comment