Projects from Totally Wicked E-Cigarettes



Projects from Totally Wicked E-Cigarettes

The basic ingredients for a project management framework may be represented schematically in Figure -1. A working knowledge of general management and familiarity with the special knowledge domain related to the project are indispensable. Supporting disciplines such as computer science and decision science may also play an important role. The representation in Figure -1 reflects only the sources from which the project management framework evolves.

Figure 1:  Basic Ingredients in Project Management

Specifically, project management in construction encompasses a set of objectives which may be accomplished by implementing a series of operations subject to resource constraints. There are potential conflicts between the stated objectives with regard to scope, cost, time and quality, and the constraints imposed on human material and financial resources(Wysocki, 2011: 47). These conflicts should be resolved at the onset of a project by making the necessary tradeoffs or creating new alternatives(Berkun 2010).

Main Requirements of the Project

To advertise and recruit required professionals.

To analyze and document the specifications for the required functionality.

To acquire the needed hardware and software as part of IT infrastructure facilities.

To design, implement, test and operate the entire system.

Next step is defining human resources in terms of category, seniority and hourly cost:

Functional expert(s) - Knows the business process

Technical support - Technical product knowledge

Workflow Business Analyst - Workflow tools expert

System Administrator- Maintain workflow environment

Business Analyst - assist in doing a business process analysis

The Number of Programmers and Designers Needed To Finish the Project

These days, the cost of the project is often fixed before the design is done, and sometimes even before design has begun. Estimation now becomes more of guesswork based upon experience that was gained by screwing up earlier estimates. Without the design, it was quite impossible to know how many lines of code/functions/components/objects would be required. The estimator should rely on data and documents available before one starts the design, such as the functional and non-functional requirements, workflows, and use-cases. Therefore, requirements gathering and analysis is very critical to the project's estimation (design, development, and testing) (Cleland 2009).

Using these documents, the estimator may create an object hierarchy tree simultaneously. The object hierarchy tree can help identify different levels/types of objects to be created, what is expected from these objects, and even some attributes for the objects. Therefore, without having an application design in place, the scope of work to be done, in terms of functionality required, can be identified (Haugan 2009).

Major Tasks to Be Carried Out

Schedule Inputs

You need several types of inputs for the company to create a project schedule:

Personal and project calendars - Understanding working days, shifts, and resource availability is critical to completing a project schedule.

Description of project scope - From this, you can determine key start and end dates, major assumptions behind the plan, and key constraints and restrictions. You can also include stakeholder expectations, which will often determine project milestones.

Project risks - You need to understand these to make sure there's enough extra time to deal with identified risks - ...