Please enable JavaScript.

Coggle requires JavaScript to display documents.

RG Training Program (Metrics & Delivereable (Weekly Meetings to review…

- - - - Strong PHP Knowledge
        Able to handle complex SQL Queries
        
        Strong understanding on how HTTP works
        
        Basic DevOps Knowledge
        Docker
        
        Basics on React
        
        Softskills
        English
- - - - Developer starts working on non-critical tasks
      - Two weeks
      - All tasks should be estimated and approved by lead
      - After finishing tasks, developer must log in accurate time for task
      - Lead needs to review logged in hours daily
      - Kickoff setting end date
      - Revision after two weeks
        
        Sucess
        
        Finished the job
        
        listened to lead
        
        Followed good practices
        
        Progress on accuracy of estimation of tasks
        
        Review if developer can jump to next phase
        
        Few improvement areas found for the developer
        
        The developer found improvement areas for the project
        
        Failure
        
        Didn't finish
        
        Delayed work
        
        Progress is not noticeable
        
        Consider repeating phase or going back to phase 0
        
        Lot of improvement areas were identified
      - Developer asks for architectural guidance
    - - Learning and training for no more than 2 weeks
      - Lead will evaluate if developer needs to pass here or if can jump directly to next phase
    - - Lead defines end date
      - Developer starts taking critical tasks
      - Client needs to be aware
      - Lead review accuracy of logged in hours weekly instead of daily
      - Revision
        
        Success
        
        Less back and forth on merge requests
        
        Estimation are more accurate
        
        Lead should have confidence on letting developer take more critical tasks
        
        Developer should be able to move around the project by himself
        
        Code quality should have improved
        
        Failure
        
        Developer can't move around project without help
        
        Still a lot of back and forth on merge requests
        
        Accuracy with logged in hours has not improved
        
        Client is not comfortable
        
        Lead doesn't consider developer fits in the project
      - Lead should consider open up communication between developer and client
    - - Could start transition if necessary
      - Developer takes critical tasks, resulting in reduced workload for the team
      - Developer has an active role within the project
      - Client is comfortable working with the developer
      - Developer starts having ownership over modules
      - Lead doesn't have the need of checking logged in hours
      - Lead should feel comfortable not having merge requests (doesn't mean it's not necessary though)
      - Revision
        
        Success
        
        Lead feels confidante developer could take over the project any given time
        
        Developer feels can take the project
        
        Client is ok with having a transicion
        
        Failure
        
        Developer's modules cant get along with other modules
        
        Developer doesn't take responsibility for his tasks
        
        Developer has troubles communicating ideas or understanding requirements from the client
        
        Developer is not constantly learning and improving
      - Developer could give a knowledge transfer to other developer
      - Revisions for next phase should take longer (Recommended 3 to 6 weeks)