Environment :: Genesis Genie

The Genesis Declaration states that the management of intangible projects is about managing the Tallent, Attitudes ,Skills and Knowledge(TASK) of individuals and the interplay of their interactions along with the processes and tools that they use. It aims to define the intangible project requirements precisely, transforming it into a set of inter connected objects and processes, that decompose into tasks , specifications and events, delivered in stages along with comprehensive documentation. It works to bring about meaningful customer collaboration that ensures transparency of project progress, tackling change while following a plan ever mindful of the contractual obligations that govern the delivery of all projects.

The objective is to create a system to define and manage projects where the resources are primarily intangible capacities.

Therefore we need an environment in which such projects are undertaken Usually there is a final objective and it is possible to describe the final objective.The main function of this project is project management. There are two types of such projects, well-defined projects where the technologies and the proficiencies required for execution are well established. The other involves investigations, emerging technologies and path-breaking procedures where the methods and time requirements cannot be easily established. The latter needs creative insights which are less easily definable. Genesis will primarily serve the first type of project in the first version.

That is, technologies are well defined, durations for tasks are easier to predict, and proficiencies needed to execute particular tasks are well defined, that is they are reasonably precisely definable, and the levels needed for tasks are also easily estimable. The environment for such projects have: a set of tangible resources (like machines, technologies, tools) locations of resources (like workstations, conference rooms, libraries) a set of intangible proficiencies (attitudes, skills and knowledge often relating to machines, technologies and tools) a set of objects that the project generates (like unit requirements, specifications, database schemas, algorithms, events, triggers, and so in software projects; can also include meeting minutes, action sheets and so on) a set of entity which usually have proficiencies proficiencies of entity vary over time.

Projects themselves have: an objective an overall time frame an elaboration of that objective a requirements document which describes what each sub-objective must achieve a detailing of each item in the requirements document that elaborates the objects that will be involved in meeting this requirement the transformation of such a detailing into a UnitRequirement, which can be break down into a set of work Specifications, with the profciency profile for their execution a set of defined resources a set of defined entity work Specifications have resources and entity assigned to them (usually one responsible entity) When more than one entity needs to work on one Specification, teams can be defined, with team leaders, and that team entity will be assigned to that Specification Specifications will have a target duration (calendar time) and a target worktime (hours to complete) Project progress monitoring can use one or more the following: Phases, and activity within them.

Phases can have hierarchies, activity have no further breakdown modules, and sections within them. modules can have hierarchies, sections have no further breakdown Control Sheets, which effectively provide the network of project execution Control sheets may identify the section Control sheets are essential in time-bound projects, since they will establish the critical path of the project As specifications attach to a control sheet, they may specification their sequence within the control sheet (by predecessor specification), and may have a weightage to that Controlsheet, implying that its completion implies completion of that percentage of the control sheet s work content. work specifications identify the activity, section and control sheet in which they are executed Project execution goes as follows: Specifications are assigned to entitities.

On assignment, the calendar date will attach to the specification, and by implication, if this is the first specification for this control sheet, the inception point of that control sheet.Total duration of the specification is the total duration of control sheet. If there is no predecessor for specification, then specification starts along with first control sheet. Cumulating duration of specification in sequence will be the control sheet duration. Specification cannot be assigned to a person if he already has one specification. Concept of total duration and actual duration must be added in specification. Specification start date and end date is derived from control sheet and it should be showed and locked in entity calendar. Entities report their work on time records.

Each TimeRecord, which is for a calendar period, will specification individual time spent on each specification, along with a work report and an estimate of progress. PaymentMethod will be defined for payment to entity. Project management involves: Change management of project objects Assignment of work and specifications to entity. specification templates are used for assigning specification. Planning of schedules, and resource/entity utilisation Management of resources and entity over time Project control involves: Access control of entity to project objects, locations and resources Monitoring of time records entered Alerts on non-compliance or deviation from plans or schedules Organisation and Administration As a system, Genesis will be enabled for organisations to undertake multiple projects following an overall work ethic.

The control of the work ethic will be done by the Organisation Administrator, who will set up the work ethic by defining the limits and bounds of various parameters that affect various elements across projects. As example, maximum specification duration, status definitions, specification role structures and access levels, and so on. Access menu for each role is also determined by the administrator.For the Genesis Project, specificationally, the SVN ( repository ) folder will have sub folders Requirement, Specification, Structure, Process, Discussions, Manuals, Test, Code. code will follow Conventions that already described. In general, the Administrator can define folder types for the organisation, and then import subsets into particular projects. It needs to be considered whether (and how) this will have a hierarchy.logs also be maintained.netmon is software, that allows keeping and tracking statuses of resources.