Skill level required for a successful conversion


The skill level of the developer will make or break the project regardless of the "conversion" issues.

I am a better hockey coach when Wayne Gretzky is on the team.


Hence the #1 consideration is at what level the developer is at. There are certainly more levels then just "trained" or "not trained". Generally there are a "lot" of skill levels, but the following breakdown is sufficient. **

    Stage 1 Innocent (never heard of the product)

    Stage 2 Aware (Has read an article about X)

    Stage 3 Apprentice (has attended a three-day seminar)

    Stage 4 Practitioner (ready to use X on a real project)

    Stage 5 Journeyman (uses X naturally and automatically in his job) 

   Stage 6 Master (has internalized X, knows when to break the rules) 

   Stage 7 Expert (writes books, gives lectures, looks for ways to extend x)


One should NEVER attempt a project with a team consisting with Stage 3 or lower people. This is a sure fire formula for failure. The team can consist of stage 4's, but they should have at least access to Stage 5, or 6. This requirement is needed both in Pick and Ms-Access.


Ok, I think I made a big enough point about skill level (however, a good developer means everything). Now, lets get on with some of the issues of converting a application from Pick to ms-Access.

[Image][Image]
[Image]
[Image]
 
 
** Page-Jones, Meilir. "The Seven Stages of Expertise in Software Engineering", American Programmer, July-Aug 1990