www.lean-tech.

io

Custom Software Development
Need a customized solution? We can
take it from zero to hero in no time.
Machine Learning
We research and develop new
technologies, like Machine Learning
and AI.
What we do best
Our Solutions
Staff Augmentation
Nearshore solution for all your
development needs
Database Architecture Design
We design and implement database
structures to support your business
processes.
Design UI/UX
Seasoned design teams to make
your applications stand out.
Software Administration
You are probably going to want
expert administrators to manage
your applications…
We have them too.
Automated QA
We automate your tests and keep
your application running smooth
all year long.
Training & Education
We are empowering our next
generation of engineers and
software developers by providing
training grounds for their
continued growth
Project Managed Business
Dedicated Services

How the branch works

Objectives:
● Deliver on-time
● Customer visibility (TRELLO)
● Happy and interested employees

SCRUM Master

Customer Manager

Development Team
Dedicated Services Branch
 Team Services

“
We provide an exceptional nearshoring
experience and act as an enabler for
companies who want to create incredible
applications.

”
PM Services

“
The customer does not have an IT department on
our end. They are expecting a finished product and
do not mind actually how it’s done

”
Dedicated Services

How the branch works

Manager/
Supervisor
Objectives:
● Customer Retention
● Customer Satisfaction
● Transparency and fluent communication with the customer

Cell Lead Development

PM Accounts work like PMB. Team should not hold any communication directly with the Customer Team
customer without the supervision of the manager and even less if that will change the scope
of the project.
Team Accounts need constant communication between all parties.
Manager should guarantee a fluent and smooth communication between
the leader and the customer.

SCRUM
Customer Manager/ Master
Supervisor

Cell Lead Development

Team
Dedicated Services

Onboarding Agenda
Dedicated
Development
Groups
TQA Department
Operations Department

Technical Quality Assurance Department

11
Account Management
Basic Operations Structure

Accounts Organization

6 4
Maximum number of Maximum number of
accounts per manager accounts per SCRUM
Master

1 PO
Projects per Lead Account Manager in
Developer SCRUM

1 TL
Projects per developer Lead Developer in
SCRUM
13
Basic Operations Structure

Account Manager Job Description (PO)

Job Responsibilities Job Duties
- Keep a fluent and smooth communication with the customer, making him feel - Deliver reports every two weeks with the status of the account and each
happy and meet their expectations developer, this report must include the one delivered by the supervisor together
- Do and document the requirements gathering process for new projects and existing with how the project is regarding the established timelines and how is it
projects matching the customer expectations
- Plan and implement projects - Weekly meetings with the customer (Reports (Demo Meeting) and
- Help define project scope, goals and deliverables Requirements gathering (Refinement))
- Define tasks and required resources - Have at least 1 meeting with the team for keeping track of the product status
- Collect and manage project team - Keep updated his manager TRELLO board almost on a daily basis
- Allocate project resources - Keep the customer’s TRELLO board updated
- Create schedule and project timeline - Interview new developers he would like to assign to his accounts
- Track deliverables - Be part of the manager’s meeting for Lean Tech newbies.
- Support and direct team from a professional and a personal perspective - Participate as PO for development of projects for PM Dedicated accounts and
- Lead quality assurance PMB accounts: POVW document, User Stories Creation, Define Cronogram,
- Monitor and report on project progress on PM tools like TRELLO Wireframes, Flow Diagram.
- Present to Director of Operations reports on progress as well as problems and - Manage all augmented services with the TQA Manager, initial projects and
solutions requested by the team (TBD process and format)
- Implement and manage change when necessary to meet project outputs - Choose the Lead Developer for each team with the support of the TQA team.
- Evaluate and assess result of project - Request developers for their accounts (TBD process and format)
- Keep updated, with the help of each lead developer, the project documentation from - Be part as a PO of all planning meetings and provide the information with at
a tech and a user perspectives least two days of anticipation of the meeting
- Be part as product owner on all Sprint Review Meetings for PM accounts

14
Basic Operations Structure

Lead Developer Job Description (PO and TL)

Dedicated
Job Responsibilities
- Direct communication with the customer
- Take up the responsibility of the entire Project
- In charge of following customer’s methodology
- Reporting for all the weekly tasks in form of accurate and detailed reports
- In charge of each developer’s workload
- Implementing the best practices and coding standards of the project.
- To keep a check on the whole system, conduct the testing and integration testing for
the entire system
- Optimization of the application for maximum speed and scalability
- Writing and implementing efficient code
- Maintaining and upgrading existing systems
- Training new developers assigned to the specific account
Job Duties
- Fill out reports every two weeks with the status of the account and a review of
each developers. (Report Template TBD Include Retrospective meeting)
- Have at least 2 meetings with the customer per week and share the meeting
resolutions with the Account Manager. (Meeting Report TBD)
- Code review for each developèr’s commit/task including:
- Code formatting
- Architecture
- DRY
- Best practices
- Readability, Testability, Debuggability, Configurability
- Identifying bugs
https://www.evoketechnologies.com/blog/code-review-checklist-perform-effec
tive-code-reviews/
- Keep the PM tool updated (i.e. Jira, Trello, etc)
- Interview and train new developers with Lean Tech and customer’s standards.
- Be part of the supervisors meeting for Lean Tech newbies.
- Participate as PO for development of projects that do not depend directly on
the customer: User Stories Creation, Define Cronogram, Wireframes
- Request augmented services to their account manager in case the customer
approves it. (TBD process and format)

15
Basic Operations Structure
Lead Developer Job Description (TL)
PMB and PM
Job Responsibilities
- No Direct communication with the customer
- Take up the responsibility of the entire Project
- In charge of the quality of its technical deliverables
- Establishes a technical vision with the development team
- Carefully analyse the project and rectify the errors found in the process
- Reporting for all the weekly tasks in form of accurate and detailed reports
- Implementing the best practices and coding standards of the project.
- To keep a check on the whole system, conduct the testing and integration
testing for the entire system
- Optimization of the application for maximum speed and scalability
- Writing and implementing efficient code
- Maintaining and upgrading existing systems
- Training new developers assigned to the specific account.
- Break up projects into digestible tasks, to tie those tasks to iterative
deliverables, and to keep track of those deliverables
- Work to resolve technical disputes.
- Watchful of technical decisions that have long-term consequences.
- Tech Lead works closely with the Account Manager to build an ideal work
environment
Job Duties
- Fill out reports every two weeks with the status of the account and a review of
each developers. (Report Template TBD Include Retrospective meeting)
- Inform immediately the Account Manager with any exception, delay or issue
with a developer or the project itself.
- Inform the SCRUM master how the project is going.
- Check that the project’s architecture is been followed correctly.
- Proactively participate on each Sprint Planning meeting, helping developers to
define the best way to accomplish a specific US and divide correctly each user
story in the tasks needed.
- Code review for each developèr’s commit/task including:
- Code formatting
- Architecture
- DRY
- Best practices
- Readability, Testability, Debuggability, Configurability
- Identifying bugs
https://www.evoketechnologies.com/blog/code-review-checklist-perform-effec
tive-code-reviews/
- Train new developers with Lean Tech and customer’s standards.
- Be part of the supervisors meeting for Lean Tech newbies.
- Request augmented services to their account manager. (TBD process and
format)
16
Basic Operations Structure

Lead Developer Soft Skills

- Sincere empathy
- Technical excellence
- Excellent communication skills
- Excellent understanding of the product
- Able to balance the demands of managing a team and contributing code
- Excellent understanding of the business problem the software is solving
- Excellent understanding of the field the software's users are part of (medical, HR, etc.)
- Team Player
- Understanding of other disciplines like management, product development, marketing, etc.
- Excellent english level: B2 for Dedicated accounts and B1 for PM & PMB accounts

17
Basic Operations Structure

How does all that work together?

1 4
Maximum number of Maximum number of
accounts per Lead accounts per SCRUM
Developer Master

10 10
Maximum number of Maximum number of
accounts per Architect accounts per DevOps

3 5
Maximum number of Maximum number of
accounts per QA accounts per UI/UX
18
Account

Account Manager Trello Board - Accounts

Account Card Fields/Attachments (Ded, PM & PMB)
- Account Dropdown
- Developers
- Lead Developer
- WFH Logbook (Drive Document)
- Forecast (Drive Document)
Project Fields (PM & PMB)
- Start date
- End date
- Project Status
- Status (%)
- Chronogram (JIRA Photo Attached)
- Project Overview (Drive Document)
- JIRA link 19
Account

Account Manager Trello Board - Developers

Developers Card Fields

- Account Dropdown
- Due Date (Transition Date)
- Start Date
- Matrix Status
- Seniority & Technologies
- Performance Review Excel File 20
Account

Customer Side
What you will find in this board?
(Ded, PM & PMB)
- How to use Trello
- Active Projects
- To-do/Doing/Done
- Customer Meetings & Reports
- Account Resources (Documentation)
(PM & PMB)
- Views & Features Approval Process
- Project Status and Chronogram
(Ded & PM)
Other Channels: - Candidates and Interested In Process
- Your team

21
Account

Forecasts

What will you find here?

- Hours worked per day
- Project Forecast
- Project Status Health
- Total Project Costs

22
Account

Developer Transition - Operations Side

23
Account

Developer Transition - Developer Side

24
Project Execution
Project Execution

Requirements Gathering - Customer Side

Requirements Requirements Planning & Analysis Project Execution

Gathering 1 Gathering 2 Deliverables Agenda (Trello)

- Project methodology
- Project overview - Final questions and
- Application user stories
- Current state context doubts - Full Project Overview
- A complete backlog of
questions - Presentation of project Document filled out
what needs to be
- Current state business tools including Project - Wireframes
completed
process questions Management and - Chronogram
- Roadmap
- Identify problems Development
- Wireframes explaining
- Opportunities for Management
the app workflow.
improvement applications.
 Basic Operations Structure

Project Planning
- Project overview document
- Call recordings
- POVW Document
- Customer needs - Guidelines Approved
and requirements - Proposal Information and
- Proposal - Planning Output
- Video recording documentation

Input

Output

0 0 0 1 2 3 1 2 3 2
Requirements Lean Tech Guidelines
Prospecting Preparation Proposal Planning Square Approval Design
Gathering Creation
1 2 3 4

Execution

Participants:
Project Overview Document First - User Stories - ERD
- Wireframes - Approved Square
Draft - Architecture
- Cronogram Certification and Report
Manager 1
- Code Audit Schedule
TQA 2 - Servers and dev
environment running
Scrum Master 3 - Approved POVW document - UI/UX Views cronogram
- SCRUM Guidelines (Example User (Sprint -1))
Team 4
Stories and how to document) - QA testing plan
- How to create and ERD document
- How to create a Soft. Ing Document
Department in charge: - How to create a wireframe document

Square
Project Execution

Planning & Analysis Deliverables

- Project Overview
https://docs.google.com/document/d/13BKZMvAFR4CP68GJciC30dU0qPTQrHtzJMwZROUxml4/edit

- Wireframes
https://docs.google.com/presentation/d/1aNTlz_PsX2ATLevy9Y4tJlxTRjYV1dGCPOF-ferXNB8/edit#slide
=id.g7dfff38f74_0_724

- JIRA User Stories

https://starkcore.atlassian.net/jira/software/projects/EL/boards/12/backlog
Basic Operations Structure

Sprints & Planning

● Monthly Code audit ● 2 weeks sprint
● Updated Trello Board by Manager ● Individual performance report
● SCRUM reports (On-track or not) Participants:

Manager 1

Square 2

Backlog with
Scrum Master 3

estimates, customer Team 4

requirements and SPRINT PLANNING SPRINT REVIEW

cronogram. Sprint - 3 1 4 3 1 4
1 concept for
refinement

1. Customer Status
EXECUTION AND SPRINT Report
2. Updated Trello
STAND-UPS REPORTING
1 3
3 3. SCRUM report

29
 Basic Operations Structure

SCRUM Methodology - Tickets Lifecycle

1 2 3 4 5 6

Backlog Analysis Code QA POR Done

All tickets to be done on the Tickets that are been analyzed
running sprint with an by the developer, he must
assigned developer provide a approach before
begin coding and the approach
must be approaved by another
dev
Tickets in which the Tickets on the dev Product Owner review, he All completed and approved
developers are currently environment, the QA is must approve that the ticket tickets, tickets in this column
working on currently evaluating them and actually matches what the will be find on the production
trying to find bugs customer was requesting environment
Project

Project Delivery

- Complete User Guide and Project Delivery Status document

- API Documentation of the application.
- Backend Document: Architecture and general information
- QA Report and Certification Letter of the performed tests. This report also includes the known bugs Lean Tech
is going to address and release in future versions of the application with possible improvements and features.
- Production URL

31
Do you have an outstanding idea to power up your business?
Thinking outside the box?

Come and join us, we will develop it for you.