Module -3

Design Thinking in IT
• Design Thinking to Business Process modelling
• Agile in Virtual collaboration environment
• Scenario based Prototyping
Business Process Modelling (BPM) :
Definition:
• Business Process Modelling (BPM) is a method of visually representing an organization’s business processes by
breaking them down into fundamental components- such as functions, actions, and workflows.
• It provides a clear and concise view of how a product or service moves and transforms through various stages
within the organization.
Purpose:
BPM aims to facilitate better understanding and analysis of business processes.
It enables businesses to:
Identify inefficiencies,
Streamline operations,
Communicate processes effectively among all stakeholders.

Stakeholders Involved: (interest in company’s operation , decision, and outcomes)

• Business Analysts
• Process Partners
• Developers
These models foster collaboration and shared understanding, ensuring everyone contributes effectively
to process-related tasks.
Key Steps in BPM:
[Link] Mapping: Visual representation of the current process flow.
[Link] Detection: Identifying existing and undocumented processes.
[Link] Imitation: Simulating processes to understand workflow behavior.
[Link] Analysis: Studying processes for inefficiencies and areas of improvement.
[Link] Development: Redesigning or optimizing processes for better performance.

Advantages of Business Process Modelling:

Aligns Operations with Business Strategy: Ensures that day-to-day operations support broader organizational goals.
Improves Process Communication: Enhances understanding and collaboration among stakeholders.
Increases Control and Consistency: Standardizes processes across departments.
Improves Operational Efficiencies: Identifies and removes inefficiencies.
Provides Competitive Advantage: Enables faster, more adaptive responses to market changes.
Real-Time BPM Example: Hospital Appointment Scheduling System

Scenario:
A hospital uses a mobile app or web portal for patients to book appointments with doctors.

Process Name: Patient Appointment Scheduling

BPM Steps:
1. Process Mapping:
Visual diagram of the steps: Login → Select Department → Choose Doctor → View Availability → Book Appointment →
Receive Confirmation.
2. Process Detection:
Identifies that patients also call the reception or visit in person—those processes are now integrated into the same
system.
3. Process Imitation:
Simulate booking flow to test user interactions, appointment load, and delays in doctor availability.
4. Process Analysis:
Analyzing where delays happen (e.g., overlapping bookings, patient wait times) using app analytics.
5. Process Development:
Automate confirmation messages, integrate doctor calendar sync, and reduce manual steps through automation.
Benefits Achieved:

BPM Advantage Real-Time Application

Align operations with strategy Focus on digital transformation & patient experience

Improve communication Real-time notifications to patients and doctors

Increase control & consistency Standardized booking flow for all departments
Improve efficiency Reduced workload for front desk and faster bookings
Attract more patients with smoother digital
Competitive advantage
experience
Design Thinking in Business Process Modelling (BPM):
Integration of BPM and Design Thinking:
Business Process Modelling (BPM) provides a clear picture of how things are done within an organization
by mapping out existing processes.
• It helps identify inefficiencies, bottlenecks, and opportunities for improvement by:
• Highlighting dependencies
• Revealing interpersonal relationships
• Analyzing the interaction between people, process, and technology
• This analysis serves as the foundation for process optimization.
Key Differences & Synergy
Aspect BPM Design Thinking
Focus Internal process improvement Human-centered innovation
Empathetic, creative problem-
Approach Analytical, process-based
solving
Goal Efficiency, standardization User satisfaction, innovation
User interviews, observations,
Data Source Workflow maps, system data
feedback

When combined :
BPM helps uncover what is happening, and
Design Thinking reveals why it's happening from the user’s point of view.
How Design Thinking Enhances BPM

1. Empathy Mapping:
Understand the emotions, needs, and pain points of the end users interacting with a business process (e.g.,
customers, employees)

2. User Journey Mapping:

Go beyond system workflows and trace the actual user experience, capturing touchpoints and moments of frustration
or delight.

3. Ideation Workshops:
Collaboratively brainstorm with stakeholders to reimagine better workflows using creative thinking, not just efficiency
metrics.

4. Rapid Prototyping:
Test new process changes (e.g., self-service portals, streamlined forms) with real users before full implementation.

5. Feedback Loops:
Use continuous feedback to refine both the process and the user experience iteratively.
Agile in Virtual Collaboration:
Agile is a project management and product development approach are widely embraced in the software industry
focused on flexibility, collaboration, and delivering small, incremental improvements continuously.
Agile Works
• Agile breaks work into smaller units (often called user stories) and organizes them into short cycles called iterations or
sprints (usually 1–4 weeks). At the end of each sprint:
• Teams deliver a working piece of the product
• Stakeholders provide feedback
• The team reflects on how to improve
 Iterative progress through sprints, Continuous feedback and improvement, Close collaboration between teams and
customers, Quick adaptation to change.
Agile Frameworks:
 Scrum: Uses sprints, roles like Scrum Master and Product Owner, and regular ceremonies (e.g., daily stand-ups, sprint
reviews).
 Kanban: Visualizes work on a board, focuses on continuous delivery, and limits work in progress.
 Extreme Programming (XP): Emphasizes technical excellence and practices like pair programming and test-driven
development.
 SAFe (Scaled Agile Framework): Scales Agile across large organizations.
When to Use Agile
Agile is ideal use: Requirements are likely to change,
• Speed and flexibility are priorities,
• Stakeholders need frequent involvement,
• Projects are complex and need regular adjustments.
Benefits of Agile
• Faster time to market
• Better product quality through frequent testing
• Higher customer satisfaction due to continuous feedback
• Greater team collaboration and transparency
• Easier to adapt to change
Agile principles : Agile principles and practices within remote or distributed teams using digital tools and communication
methods. to make Agile effective in remote teams:
1. Allow Openness
• Foster transparency at every level of the organization.
• Empower team members to make decisions aligned with the company's vision and goals.
• Keep responsibilities clear, results visible, and decision-making inclusive.
• Create open communication channels to share feedback and insights freely
2. Establish a Culture of Continuous Improvement
• Encourage every team member to identify and suggest opportunities for improvement.
• Regularly reflect on what’s working and what isn’t.
• Use Agile retrospectives and small experiments to guide change and innovation.

3. Prioritize Communication
• Communication is the backbone of effective virtual collaboration.
• Go beyond emails and meetings—use real-time tools (e.g., Slack, Teams, Zoom) and collaborative platforms (e.g., Jira,
Confluence).
• Ensure consistent updates across all levels of the organization.
• Emphasize deep communication: listening, feedback, and clarity of purpose.

4. Rhythm Building:
• Establish a predictable Agile workflow that aligns with the three Scrum pillars: transparency, inspection, and adaptation.
• Maintain regular sprint rituals (e.g., daily stand-ups, planning, reviews, and retrospectives).
• Clarity, testing, and flexibility are key to sustaining momentum in fast-paced virtual environments.
5. Develop a culture of courage and flexibility
• Encourage experimentation and accept that failure is a path to learning.
• Promote rapid prototyping and “failing fast” to reduce time wasted on ineffective paths.
• Support team members who take initiative and adapt quickly to new challenges.

6. Establish a stable environment and work life balance

• Avoid burnout by respecting team members' working hours across time zones.
• Set clear rules for availability, expectations, and workload distribution.
• Promote a healthy balance between work and personal life to keep morale and productivity high.

7. Visualize the Workflow

• Use task boards and digital dashboards to provide visibility into project status.
• Ensure team members can track progress, assign priorities, and identify blockers.
• Tools like Kanban boards, burn-down charts, and real-time dashboards help ensure accountability and continuous
process improvement.
Scenario-Based Prototyping :
• Design thinking emphasizes rapid visualization and iteration of ideas through tangible prototypes. This approach works well for physical
products and straightforward digital tools.
• complex software systems, especially those involving multiple user roles and interactions.
• scenario-based prototyping emerges as a valuable method. It uses structured models—both structural (data, architecture) and
behavioural (user interactions, workflows)—to represent complex systems.

Key Aspects of Scenario-Based Prototyping

1. Model-Driven Design
• Utilizes formal models to represent software structures and behavior.
• Encourages step-by-step enrichment, meaning the prototype evolves iteratively based on insights from previous design phases.
• Promotes interoperability between models, ensuring consistency across various layers of design.
2. Bridging Design and Engineering
• Models act as a blueprint for low-level system development.
• By aligning design artifacts (e.g., flowcharts, use cases, UML diagrams) with actual development steps, the gap between design and
engineering is significantly reduced.
3. Realistic Scenarios
 Scenarios illustrate sequences of events or user actions as they would occur in real-life contexts.
 They reflect the dynamic behavior of one or more users interacting with the system.
 This helps capture edge cases, errors, and exceptional flows that static prototypes may overlook.

4. Two Types of Scenarios

 Use Conditions: These are current-state scenarios derived from how systems or users behave in real-world settings today. They serve as
analytical baselines.
 Design Conditions: These are future-state scenarios, representing improved or modified versions of use conditions. They reflect the
system as envisioned after design intervention.

Benefits of Scenario-Based Prototyping

 Supports complex, multi-user interactions that are difficult to visualize with static wireframes or mockups.
 Encourages iterative feedback and evolution of ideas.
 Ensures better alignment between user needs, design intent, and final implementation.
 Facilitates early testing and validation of concepts without needing fully functioning systems.