DICAM Methodology

ICDAM: Internal Company Development Agile Methodology.

ICDAM is an agile methodology that can be applied to internal company departments. The current agile methodologies are focused on companies that only generate program. ICDAM is focused for giant companies that have internal development departments.

ROLE DEFINITION:

There can be more people in the team (mixed-roles) but it is so important that the following roles are in the team. In this technique there are main roles:

The wizard: this role is applied to the who has the most technical knowledge in the department.

This role has main duties in a department:

1) analyze which is the best way to implement a project using the technical resources obtainable in the company. Plenty of times the company resources are limited, so then the wizard has to choose the best way to make use of these resources to implement a project. Before to start making a used Project, the wizard has to measure the company resources to make the new project, how the project must be apportioned & the best expertise (java, net. perl, etc.) to generate this project in the company's surroundings.

2) Try to improve & upgrade the company tools (for example try to upgrade java version, server versions etc.). They are the who looks for new versions of company tools.

3) Share his knowledge with the remainder of the team.

The knight: this role is applied to individuals who have the most business knowledge in the company. This person is normally to be the oldest person in the department. This role has main duties in the department:

4) After the know-how measures are select for the new Project, they are to propose which is the best way to generate the Project according the type of users. They are the who knows better the company users.

5) Check that the new projects are adeccuated with the company business

6) Check if there were an outside adjust that affects the company business, they will document to the remainder of the team the changes to make in any involved projects.

6) share his knowledge with the remainder of the team.

The King: this role is normally the boss of department. The King decides the best way to resolve issues between the wizard & the knight if there was no agreement on how to generate the project. The king rules, they is the King after all.

HOW TO WORK:

New project: Before to start to make a used project, the wizard will spend a day or searching the best technical way to make the project according to company resources.

The next stage: the wizard & the knight have a gathering or hours), & they must select how to focus this project, if the wizard, & the they knight do not agree, the King must select the way it will be done.

Diary meeting: Every day they must meet to speak about the projects of the department, new versions of tools, & out of doors changes that affect the department project requirements in their department.