WEEK 03 — DIGITAL TRANSFORMATION
Change Management & Agile Methodologies
Exploring data-driven strategies, frameworks for organizational change, and iterative agile processes like Scrum.
CHAPTER 01
Data Analytics & Strategy
How prescriptive analytics and data-driven insights form the foundation of strategic decision-making in business, exemplified by the Netflix transformation.
CASE STUDY
The Transformation of Netflix
Netflix shifted from a traditional movie rental business model to streaming on demand, fundamentally changing the movie industry. This required adapting to cloud infrastructure, video encoding, and navigating competition and piracy.
PRESCRIPTIVE ANALYTICS
- Descriptive: What happened?
- Diagnostic: Why did this happen?
- Predictive: What might happen in the future?
- Prescriptive: What should we do next?
CHAPTER 02
Change Management
Change management ensures that organizations smoothly transition to digital transformation by aligning people, processes, and technology.
FRAMEWORK
Navigating Organizational Change
Transformation goes beyond technology. It requires structured change management to overcome resistance, foster support, and ensure that new processes are integrated deeply into the corporate culture.
KOTTER'S 8-STEP MODEL
Create Urgency
Highlight the importance of change and the risks of staying the same.
Build Coalition
Form a group of influential people to lead and drive the change effort.
Strategic Vision
Develop a clear vision and outline initiatives to achieve it.
Communicate
Share the vision and strategy constantly with all stakeholders.
Empower Action
Remove obstacles and provide training to help employees act.
Short-Term Wins
Create and celebrate early successes to build momentum.
Consolidate Gains
Use credibility from early wins to tackle larger initiatives.
Anchor in Culture
Ensure the changes become permanent practices and behaviors.
How can leaders effectively create urgency without causing panic or resistance?
Class Discussion
INDIVIDUAL FOCUS
Prosci ADKAR Model
The ADKAR Model focuses on the individual aspects of change. To achieve successful change, individuals must reach five key outcomes: Awareness of the need, Desire to support it, Knowledge of how to change, Ability to implement, and Reinforcement to sustain it.
CHAPTER 03
Agile Project Management
A flexible and iterative approach that accommodates change and delivers value efficiently.
COMPARISON
Traditional vs. Agile
Traditional PM relies on detailed upfront planning, assuming stability and clear end goals. Changes require formal processes, and success is measured by adherence to the original plan and budget.
Agile PM emphasizes a flexible vision, learning, and continuous adaptation through small, manageable iterations. Success is measured by delivering incremental value, even if the end goal shifts.
Why do traditional project management methods often struggle to adapt to rapidly changing requirements?
Class Discussion
CHAPTER 04
Scrum Methodology
An Agile framework for iterative and incremental development, popularized in software engineering.
ORIGINS & PILLARS
The Foundations of Scrum
The term "Scrum" originates from rugby, where players pack closely together to restart play. It reflects the importance of teamwork, collaboration, and collective responsibility.
EMPIRICAL PROCESS CONTROL
Empirical Process
Making decisions based on what is known, supported by transparency, inspection, and adaptation.
Self-Organization
Cross-functional teams manage their own work, fostering accountability and ownership.
Collaboration
Regular ceremonies (Daily Scrums, Reviews) promote communication among stakeholders.
Value-Based Priority
Focusing on delivering the most important features first to maximize ROI.
Time Boxing
Fixed time limits for activities (like Sprints) create urgency and maintain focus.
Iterative Development
Small, incremental cycles allow for regular feedback, learning, and continuous adjustment.
METHODOLOGY
Roles, Events, and Artifacts
Overview of the Scrum Process
The Sprint Cycle and Events
Roles
- Product Owner: Represents stakeholders, manages the product backlog and vision.
- Scrum Master: Facilitates the process, removes impediments, shields the team from distractions.
- Development Team: Cross-functional group of professionals that delivers the product increment.
Events
- Sprint: A time-boxed iteration (1-4 weeks).
- Planning: Deciding what work from the backlog to include in the sprint.
- Daily Scrum: Short 15-minute synchronization meeting to identify impediments.
- Review: Demonstrating completed work to stakeholders for feedback.
- Retrospective: Reflecting on the sprint process for continuous improvement.
Artifacts
- Product Backlog: Ordered list of all desired work, features, and fixes for the product.
- Sprint Backlog: Subset of items selected from the product backlog for the current sprint.
- Increment: Sum of all completed backlog items that meet the "done" criteria.
CONCLUSION
Summary
Digital transformation demands both effective change management and adaptable project execution. Frameworks like Kotter's 8-Step and ADKAR guide organizational transition, while Agile and Scrum empower teams to deliver continuous value in complex environments.
KEY TAKEAWAYS
- Change management aligns people and culture, crucial for adopting new technologies.
- Agile project management embraces uncertainty by valuing iterative development over rigid upfront planning.
- Scrum provides a structured yet flexible framework to foster collaboration, self-organization, and rapid delivery.