Knowledge Management in TCS

1. KNOWLEDGE MANAGEMENT
ASSIGNMENT
Submitted by:
Allan V Jose
A - 65
15020441031
1
Submitted to:
Prof. Supratik Ghatak

2. Pre-Agile
u Scrum:
u Scrum emphasizes empirical feedback, team self management, and
striving to build properly tested product increments within short iterations
u Scrum has only three roles: Product Owner, Team, and Scrum Master
u Waterfall
u The waterfall model is a sequential design process, used in software
development processes, in which progress is seen as flowing steadily
downwards (like a waterfall) through the phases of conception,
initiation, analysis, design, construction, testing,
production/implementation and maintenance.
2

3. Waterfall Requirement
Design
Development
Testing
Maintenance
3
• Here the customer is addressed
only after the end of the project
• Testing is done until the end of
roll out
• In Case of any issues, the
customer could address it only
after the end product
• This took a lot of time and effort
• Costly and less efficient

4. AGILE
u What Is Agile?
u Agile methodology is an alternative to traditional project management,
typically used in software development. It helps teams respond to
unpredictability through incremental, iterative work cadences, known
as sprints. Agile methodologies are an alternative to waterfall, or
traditional sequential development
4

5. Agile in TCS
u TCS’ Agile consulting services are designing and
applying Agile concepts to accelerate time to
market while aligning the products as per
customer expectations with quality
u The whole documentation process is reduced to
a great extent
u Everyone has got equal responsibility in Agile, the
role of a single manager has reduced as each
employee has an equal share of the work
allotted and executed by him
u They have successfully delivered and saved
massive time in multiple projects handling at the
same time
u Now they take the specified certified people
with them while meeting the customer, thus
gaining more projects and delivering high quality
work at the same time
5
Save Time
Quality of
work
Customer
expectations
Equal
Responsibility
Aligning
The product
Maximum
Efficiency

6. Disadvantages
u Active user involvement
u The user representative’s time and require a big commitment for the
duration of the project
u Agile requirements are barely sufficient
u This means less information available to new starters in the team about
features and how they should work. It can also create potential
misunderstandings if the teamwork and communication aren’t at their
best
u Frequent delivery
u Since the products are released at each phases, it needs constant
updating and delivering of products every time the customer comes up
with a query
6

7. Business Scenario:
u The bank faced the following challenges:
u Deploying large chunks of process change across business units,
placing the operations under severe stress
u Bottlenecks in process reviews, rework due to inadequate
requirements validation and a lack of coordination between
work streams, leading to integration issues
u Poor user adoption of new processes, adversely affecting rollout
7

8. TCS Solution: 8
u TCS’ approach allowed the work on
enhancements to evolve over the course
of development rather than planning a
“waterfall” development-based “big
bang” release.
u We emphasized on maintaining shorter
planning horizons to allow the bank the
flexibility to meet its changing demands
faster. We encouraged collaboration
across the teams to let team members’
assumptions surface early for scrutiny and
validation, significantly reducing the
need for rework later.
Key Benefits:
v A 50% reduction in process
change deployment time
v A 40% reduction in review cycle
times
v A 50% reduction in the time taken
for status meetings

9. Thank You
9