Agile Lab is in the process of creating internal systems to manage all the crucial information to run the company. The final goal is to have all our business processes mapped in online applications that generates data that we can leverage to run analysis, forecast, audit, etc.
All these application need to be organized in order to track relevant events across all the business processes, to do not lose information.
This is the actual list of application that have been internalized
Ladder Management
Goal: Manage end-to-end the individual ladder paths of our employees
Stakeholder: CTO
App Maintainer: Internal IT
Users: All
Tables:
- Ladder Placements: Each record represents the original placement in the ladder when we hire an Agiler.
- Ladder Promotions: Each record represents the promotion event generated immediately after the promotion committee of an Agiler
- Ladder Reviews: Each record represents the periodic review that a coach run to assess the ladder progress of an Agiler
- Expectation Progresses: Each record represents the progress on a single expectation ( Wis,Dxt,Etc. ) within a ladder review
- User Ladder Level: Each record represents the actual ladder level of an Agiler
User Ladder Level should never be modified, because it is automatically updated starting from Ladder PLacement and Ladder Promotion Events
Update Process:
When an Agiler start its journey
- CTO creates a record in Ladder Placements
When an Agiler got promoted
- Agiler's coach needs to inform Engineering Director or CTO that will create a record in Ladder Promotion
Hiring Proposals
Goal: Understand the offer-fit we have into the market
Stakeholder: CTO
App Maintainer: Internal IT
Users: Hiring Managers, People LeadLink
Tables:
- Hiring Proposals: Each record represents a proposal made to a candidate during the Hiring call of the Hiring Manager
- Hiring Proposal Accepted: Each record represents an offer accepted by a candidate
Update Process:
When the Hiring Manager call a candidate to make an offer
- The Hiring Manager creates a record in Hiring Proposal
When a candidate accepts an offer
- People user inserts a record in Hiring Proposal Accepted
Salary Review
Goal: Keep track of Salary progression of Agilers
Stakeholder: CTO, Engineering Director, People
App Maintainer: Internal IT
Users: Engineering Director, BU Leads, Circle Leads
Tables:
- Salary Increases: Each record represents an event of salary increase that could happen for several reasons
- User Compensation: Each record represents the actual compensation of Agilers ( all types of contracts )
The table User Compensation should never be modified, because it is automatically updated when a new Salary Increase event is created
Update Process:
When an Agiler get promoted in the Ladder and salary must be aligned to the uppder band
- The Engineering Director create a new record in Salary Increases
When an Agiler get a Salary Review
- The Engineering Director create a new record in Salary Increases
User Database
Goal: Keep track of all employees and contractors anagraphic infomration
Stakeholder: Engineering Director, Finance, People
App Maintainer: Internal IT
Users: People
Tables:
- User Extension: Each record represents the full set of information for each employee or contractor
- Resignations: Each record represents a resignation from an Agiler ( only employees )
Update Process:
When an Agiler start its journey in Agile Lab
- People Adminsitration creates a record in User Extension
When an Agiler resigns
- People Administration creates a record in Resignations table
Other capabilities
People users can updates records during the user life-cycle and can monitor the expiration of medical health checks and documents