lawro
Technology Consultants for the Smaller Business
lawrence@lawro.com
lawrence@lawro.com
Project Management in Small companies is just like big companies, only with fewer resources and less margin for error. When the owner has so many responsibilities and feels unable to delegate, we often find that there is insufficient focus on Project Management discipline. By nature many entrepreneurs are risk takers and put getting things done ahead of process. Unfortunately, this sometimes results in too little planning, underestimating risks and failing to set expectations with key stakeholders.

The following are some of the Project Management mistakes that small companies often make and some guidance on how to avoid these situations.

Being too cheap with technology

Many small companies do not have the luxury of purchasing complex technologies and adopt the attitude that free is best. Instead of purchasing a new software for Project Management they will use Excel and for Collaboration they will rely on social media platforms such as Facebook chat.

The problem is that this approach provides a false sense of cost savings at the expense of lost productivity. Excel is only useful for high level task tracking � there is no document management, dependency setting or other rudimentary features that one expects from a Project Management tool. Using free social media platforms opens to the door to employee time wasting: Facebook should be checked at the door, not invited into the workplace.

Not planning for growth

Even though small companies are often managed by visionaries, owners sometimes forget that what they build now needs to take future growth into consideration. Just like it is prudent to lease an office with an option to expand, small businesses need to view Project Management through the same lens.

First, when it comes to a process or methodology, some small businesses take the approach of making it up as they go along. Perhaps there are some circumstances that warrant this approach, but companies that expect to mature in the coming future need to realize that as they add new personnel to the organization there need to be predictable processes in place.

Ignoring Project Risk

Many companies in their infancy have high risk tolerance and as they mature become more conservative in nature. Before coming up with a plan to manage risk, the small company needs to understand its source � whether risk comes from changing market conditions, under-estimation of cost or unrealistic revenue forecasts.

Risk panning is one of the core elements in any project plan and instead of dismissing risk planning as an exercise in bureaucracy, the assigned project management should develop practical plans on how to counter risk as it arises.

Prioritizing End-Results at the Expense of Process

Small companies face a lot of different pressures, ranging from managing cash flow to supporting their customers. In this environment it may be tempting to put aside formal processes at the expense of the short term goal of winning a new customer or completing a production run.

In the Project Management arena, there is an emphasis on careful planning and discipline. For the untrained project manager who is learning Project Management on the job (a common scenario), there is often resistance to understanding methodology or to be overwhelmed by the complexity of the Project Management terminology.

Small businesses may not realize that many Project Management principles are based on common sense practices that are only intimidating from a distance. Resource Planning, Floats, Work Breakdown Structure and Task Analysis are actually concepts that require a small investment in time to understand.

Failing to Assign the Right Resources on a Project

In a small company it is not uncommon for someone to have two or even three job titles. Whereas a saleswoman in a small company might also be the marketing coordinator and event planner in larger organization each of these roles will be assigned to different individuals.

While there are many benefits from multi-tasking and in some ways the creative pressure brings out the best of people, employee constraints can do significant harm to a project. If employees are not properly qualified to perform a task, the overall project could be at risk. Sometimes people have the qualification but simply do not have the necessary experience.

Small companies project managers need to realistic about the strengths and weakness of a project team and if necessary must have the confidence to set expectations with business owner about the lack of adequate project resources and the likely impact of overall results.

lawro provides a project management service specially geared to small businesses. It is perfect for businesses that have need of formal project management but cannot afford to hire or dedicate the resources. We will provide project management for your business, part-time as needed.

Need a few hours per week to launch a vital new project? We can help define the scope, the schedule, the budget, the organizations, and all the deliverables.

Getting lawro onboard, part time, is a smart investment.

Making IT Easier
Waterfall is a linear approach to software development. In this methodology, the sequence of events is something like:

  • Gather and document requirements
  • Design
  • Code and unit test
  • Perform system testing
  • Perform user acceptance testing (UAT)
  • Fix any issues
  • Deliver the finished product


In a true Waterfall development project, each of these represents a distinct stage of software development, and each stage generally finishes before the next one can begin. There is also typically a stage gate between each; for example, requirements must be reviewed and approved by the customer before design can begin.

Developers and customers agree on what will be delivered early in the development lifecycle. This makes planning and designing more straightforward.

Progress is more easily measured, as the full scope of the work is known in advance.

Throughout the development effort, it�s possible for various members of the team to be involved or to continue with other work, depending on the active phase of the project. For example, business analysts can learn about and document what needs to be done, while the developers are working on other projects. Testers can prepare test scripts from requirements documentation while coding is underway.

Except for reviews, approvals, status meetings, etc., a customer presence is not strictly required after the requirements phase.

Because design is completed early in the development lifecycle, this approach lends itself to projects where multiple software components must be designed (sometimes in parallel) for integration with external systems.

Finally, the software can be designed completely and more carefully, based upon a more complete understanding of all software deliverables. This provides a better software design with less likelihood of the �piecemeal effect,� a development phenomenon that can occur as pieces of code are defined and subsequently added to an application where they may or may not fit well.


 

lawrence@lawro.com
+1 (201) 448-7948
Home Bespoke Developer IT Advisor Project Manager Our Story Contact Us
© 2018 Wright Consultancy LLC   Privacy Policy