Case Study: Transforming to Agile Project Management Methodology

This case study explores a company's shift from traditional methodologies to agile, focusing on Scaled Agile, Disciplined Agile, and Managed Agile Development frameworks. It highlights the need for agile transformation, emphasizing benefits like improved communication, flexibility, and customer involvement. The study details changes in organizational structure, including roles, responsibilities, and budgeting, while also addressing potential risks and challenges such as business process changes, team structure redesign, and tool modification. It recommends adopting agile methodologies to enhance product quality, customer satisfaction, project control, and stakeholder engagement. Concluding that agile's process culture facilitates manageable tasks, it underscores the importance of transparency and risk management in successful project delivery. Desklib provides access to similar solved assignments and resources for students.

AGILE PROJECT
MANAGEMENT

CASE SCENARIO:
 The company is working on traditional
methodologies and wants to transform their
working culture to agile methodology.
 The transformation should takes into three
frameworks which are named as Scaled
agile, discipline agile, and managed agile
development.
 The focus should also be given on risks and
challenges associated with the new
technology and the division of roles and
responsibilities of the team members.

AGILE METHODOLOGY:
 The agile methodology works on the set of
rules, principles, and values for achieving
predictability in the delivery of the product.

NEED OF TRANSFORMING THE BUSINESS
STRATEGY TO AGILE METHODOLOGY:
 Process culture of the agile helps in breaking down the
requirement plan for easy manageable tasks.
 “Face to face interaction helps in resolving the issues
associated with the working of the project” (Hockow,
2009).
 The employees are free to carryover their functions,
roles, and responsibilities for the betterment of the
project.
 The mind-shifts of the stakeholder can be created by
the agility.
 Active participation of customers is promoted for
specifying their requirement for the effective
completion of the project.

AGILE MODEL PROPOSAL:
The phases which are included in the agile methodology
are:
 Good recruitment policy for team formation
 “Quality analyst and customers plays an important
role in goal building” (Boehm, 2010)
 Estimation of efforts and budget
 Activities associated with coding and testing
 Reviews and feedback demonstration
 Evaluation and management of risks
 Knowing the satisfaction level of all participating
parties

BENEFITS:
 Less time consuming process
 Simple approach to follow
 “Active participation of team members which
helps in increasing the satisfaction level”
(Thangasamy, 2012)
 Overcoming the problem of old practices

TRANSFORMATION IN ORGANIZATION STRUCTURE
AFTER IMPLEMENTING AGILE METHODOLOGY:
Particulars Before After
Structure of the
organization
The focus is given on
application
The focus is given
product
Business and IT
interaction
The Proxy product owner
manages the
development process
The strong product owner
manages the
development process
Division of Roles and
responsibilities
Developers and testers
are included in the scrum
team
The integration of the
roles takes place
between the team
members of the Agile
methodology. The
minimum responsibilities
are given to the project
manager. The role of
capability building is
given to the line
manager.
Planning and
budgeting
The fixed budget is
allocated to the project
The budgeting of the
project is done in venture
capital style. In this style
funding of the product
depends on the
performance of the
product in future.

RISKS AND CHALLENGES ASSOCIATED WITH THE
TRANSFORMATION OF METHODOLOGY FROM
TRADITIONAL TO AGILE:
Risk Description
Change in business
process
The business process becomes inefficient in by bringing changes due to
customer demand. The agile methodology helps in bringing flexibility in the
business processes. It helps in lowering the risks and creating maximum
value. The response can be generated by the team to the unpredictability.
The process should be
designed for agility
The function of the company can be affected by the re-designing of the
business process such as procurement, supply chain, HR, production, and
sales.
Designing of the team
structure
It is difficult to re-design the team according to the requirement of the agility
processes. The team members who should include as business analyst,
business architect, process modeller, stakeholders, line manager, project
manager, and others.
Making choice of ITSM The IT service management helps in aligning the IT services for creating the
values for the organization. The integration of ITSM should focus on IT service
library which helps in providing the features of processes, tasks, and
procedures.
Tools The modification required in the toolset. The verification of initial requirement
helps in developing intuitive interface, importing of process documents, data
and information should be available online, simulation methods should be
used for evaluating the working of the processes, and others

WORKING OF AGILE METHODOLOGY

SCALED AGILE FRAMEWORK:
It is the framework which is based on knowledge
pattern. “It helps in synchronizing the alignment and
delivery of the agile team” (Pathak, 2013). The
principles which are followed scaled agile framework
are:
 Generation of economic view
 Application of system thinking
 Assumption in variability
 Incremental approach
 Building milestone
 Visualization of work in Progress.

DISCIPLINED AGILE DELIVERY:
 “It is the decision making framework for simplifying the process decision. It
helps in streamlining the IT processes” (Lohiya, 2013). It works on achieving
the mission of the project, creating team, addressing and identification of
risks, improving processes, and enhancing existing infrastructure.

MANAGED AGILE DEVELOPMENT FRAMEWORK:
 “The Managed agile development framework helps in successful
development of partnership” (Sliger, 2016). The macro level focused
on managing the requirement of the contract.
 The flexibility and iterative approach of the agile methodology can
be achieved in micro level. “The predictability and controlling of
activities can be improved by working on the micro level.” (Popli,
2013)