Techlogix Case Study

Presented by:

M. Atif
Issa Bilal
Junaid Siddique
Mujtaba
Ali Masud
 • Techlogix was founded by Salman
Akhtar and Kewan Khawaja in
1996 in Lahore.
• Techlogix evolve on basis of an
onshore/offshore software
Company Introduction development model.
• Onshore offices were established
in Boston, New York and Silicon
valley, offshore facility was based
in Lahore.
• Company had a turnover of
around $2 Million, growing 60%
since its inception.
Techlogix Clients
 Techlogix placed 20% of its
engineering resources
Company Structure onshore in USA. Divided into
three Categories:
(Onshore)
1. Project Architect
2. Onshore Project Manager
3. Project Engineer
 Techlogix placed 80% of its
engineering resources at Offshore
Development Centre in Lahore.
Company Structure Divided into five resources.
(Off-Shore) 1. Offshore Project Manager
2. Project Developers
3. Quality Engineers
4. Project Architect
5. Control Development
Consultant
Let’s Talk – ● 1970
Waterfall Method ● Old School
● Requires a full restart
● Not feature driven
● Not Iterative – One stage must
be finished to start new one.
Let’s Talk –
Iterative Vs
Waterfall
ITERATIVE
MODEL FOR
SOFT. DEV.
ISSUES in FMS FOR ● Client Communication in
GOVT OF GUAM FMS – Middle layer of JMT
causes a lot of hindrance
● Major Changes from client
cannot be incorporated
during development phase.
Roll back phase of Waterfall
causes COST in time and
money.
● Old and obsolete Waterfall
methods.
SUCCESS FACTORS ● Iterative Methods for
FOR ENGYRO software development
● Change Request feature form
● Sprints methodology for
feature deployments on
production
● Direct communication of
Project managers with client
– Clear requirements
HELLO AGILE AND PROTOTYPING..

Unlike Waterfall, Agile is well equipped to handle the complexity and variability involved in development projects. Using the Agile
approach, teams develop in short sprints or iterations, each of which includes a defined duration and list of deliverables, but in no
particular order. During sprints, teams work towards the goal of delivering working software (or some other tangible, testable
output).
PROTOTYPING.. ● A prototype is a version of a system or
part of the system that’s developed
quickly to check the customer’s
requirements or feasibility of some
design decisions.
● So, a prototype is useful when a
customer or developer is not sure of the
requirements, or of algorithms, efficiency,
business rules, response time, etc.
● In prototyping, the client is involved
throughout the development process,
which increases the likelihood of client
acceptance of the final implementation.
SUGGESTIONS.. ● Adopt New changes in
technology processes.
● Prior the new changes using
state of the art task
management tools like JIRA.
Tell us where you didn’t get us 