User talk:Alejandro.felipe

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 develop software. ICDAM is focused for big companies that have internal development departments.

ROLE DEFINITION: There can be more people in the team (mixed-roles ) but it's so important that the following three roles are in the team. In this methodology there are three main roles: The wizard: this role is applied to the person who has the most technical knowledge in the department. This role has three main responsibilities in a department: 1) analyze which is the best way to implement a project using the technical resources available in the company. Many times the company resources are limited, so then the wizard has to chose the best way to use these resources to implement a project. Before to start making a new Project, the wizard has to measure the company resources to make the new project, how the project must be allocated and the best technology (java, net. perl, etc ) to develop this project in the company’s environment.

2) Try to improve and upgrade the company tools (for example try to upgrade java version, server versions etc). He is the person who looks for new versions of company tools.

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

The knight: this role is applied to people who has the most business knowledge in the company. This person is normally to be the oldest person in the department. This role has four main responsibilities in the department: 1) After the technology measures are decide for the new Project, he has to propose which is the best way to develop the Project according the type of users. He is the person who knows better the company users. 2) Check that the new projects are aligned with the company business 3) Check if there were an external change that affects the company business, he will report to the rest of the team the changes to make in any involved projects.  4) share his knowledge with the rest of the team. The muscle: this role is applied to people who are in the department but they haven’t any important knowledge.

The King: this role is normally the boss of department. The King decides the best way to resolve problems between the wizard and the knight if there was no agreement on how to develop the project. The king rules, he is the King after all. HOW TO WORK: New project:

The first stage: The wizard will spend a day or two searching the best technical way to make the project according to company resources. The second stage: the wizard and the knight have a meeting (one or two hours), and they must decide how to focus this project, if the wizard, and the he knight do not agree, the King must decide how it will be done. The third stage: the team split the projects in tasks,  the team  decide how long it takes to make each task, and the important  of each task in the department. If the wizard, and the he knight do not agree, the King must decide how it will be done.

There are three degree of important : 1)	LOW IMPORTANT : the task is not important but it is necessary to finish the project. 2)	MEDIUM IMPORTANT : the task is important 3)	HIGH IMPORTANT : the task is too important Score the tasks : Multiply the degree of impact * number of hours that it takes each task The four  stage: this stage will be done after

Diary meeting: Every day they have to meet to talk about the projects of the department, new versions of tools, and external changes that affect the department project requirements in their department.

Speedy deletion nomination of ICDAM: Internal Company Development Agile Methodology.


Please refrain from introducing inappropriate pages, such as ICDAM: Internal Company Development Agile Methodology., to Wikipedia. Doing so is not in accordance with our policies. If you would like to experiment, please use the sandbox.

If you think that this notice was placed here in error, contest the deletion by clicking on the button labelled "Click here to contest this speedy deletion". Doing so will take you to the talk page where you will find a pre-formatted place for you to explain why you believe the page should not be deleted. You can also visit the the page's talk page directly to give your reasons, but be aware that once tagged for speedy deletion, if the page meets the criterion, it may be deleted without delay. Please do not remove the speedy deletion tag yourself, but don't hesitate to add information to the page that would render it more in conformance with Wikipedia's policies and guidelines. Safiel (talk) 19:03, 9 September 2011 (UTC)