The first step is to setup the calendars as all calculations regarding effort, duration, etc. are based on this. If you follow the standard 8-5, 40 hours a week routine, you can probably skip this, but if your work times are different, you must set the calendars up before you do anything else.
Otherwise, all calculations get messed up and it is nearly impossible to fix it later.
The only option then is to undo all the planning done and start again from this step. Read more
Project planning is an essential step that is quite often ignored, or if followed, not followed earnestly enough throughout the project.
If you have done due diligence with your requirements and the consequent functional specification, the first step in project planning is probably already done, for the most part.
We are referring to breaking down the work into small tasks in a structured way.
The philosophy remains the same as for the development of the functional spec… Break complex modules into smaller features and each feature into sub-feature(s) till you have broken them down into tasks that take no longer than 2 days each. Read more
One of the most critical aspects of successfully executing a project is planning it, and planning must involve both tasks and resources. In addition, it is not enough to simply create a plan and start executing tasks without properly tracking the progress. Proper project reporting to all stakeholders involved is an equally important part of project delivery. Read more
Now that you have created a detailed document with features, it is advisable for you to create a traceability matrix (like the one shown here) in an Excel file matching each feature or functionality (in a column) to a requirement (in a row). This will ensure that all requirements are met.
This will also help you quickly identify which features are impacted when a change in a requirement is sought. Any time a change is effected in the requirements, refer to the matrix to identify the features impacted by the change and make appropriate modifications to the spec. Read more
According to surveys by the Standish Group, 20-25% of projects fail (or are challenged… never mind the terminology… just know that either the vendor and/or the customer is adversely impacted, and that is bad) due to poorly defined requirements.
Requirements must be absolutely clear and signed off by you and the customer. Read more
Now you and your team have the right skills and you have the essential processes in place. How you wish this powerful combination could deliver you success in all projects automatically!
The fact is, it is not good enough. Read more
…You may or may not have heard such buzzwords as Waterfall, Iterative, Agile, etc. when discussing the SDLC processes you follow. Irrespective of what anybody says, know that it is not required. Read more
So, you are worried that when an overwhelming percentage of projects fail with experts at the helm, how would you be able to cope with it with a lot less resources and time. Read more
You are a startup or a small company. Or, you are a small division in a large company. You have brilliant, motivated people on your team. Yet you are facing a lot of challenges managing your projects. Read more
