Birla Institute of Technology & Science, Pilani

Work Integrated Learning Programmes Division

First Semester 2024-2025
Assignment

Course: SE ZG544 Agile Software Processes

Group Name: Group AZ

Team Members
Name Roll number
Lakshmi Priyanka Dulam 2024TM93202
Kishore Kumar B 2024TM93164
Shravani Vijay Dhole 2024TM93071
Rishav Shekhar Sharma 2024TM93152
Dimple A A 2024TM93009

Part 1: Agile Project Planning

You are part of a Scrum team tasked with developing a mobile e-commerce application.
Complete the following:

1. Product Vision and Roadmap

a. Create a clear product vision statement for the mobile e-commerce application.

"To provide users with a seamless, personalized, and secure mobile shopping
experience that makes discovering, purchasing, and tracking products intuitive and
enjoyable, all in the palm of their hand."

b. Develop a high-level product roadmap for three major releases over the next six
months. Prioritize key features.

Over the next six months, we’ll focus on three major releases, each emphasizing essential
features for delivering an outstanding shopping experience.

Release 1: Essential Features (Months 1-2):

• User Registration & Login Procedure: Secure account setup and login using email or
social media.

• Product Search & Filtering: Display a well-organized catalog and allow users to
search and filter products.

• Shopping Cart Management: Add-to-cart functionality with item adjustments.

Page 1
 • Basic Checkout: Guided steps for checkout (address, payment).

Release 2 (Months 3–4): Improved User Experience:

• Order tracking: Allow users to track order status.

• Payment gateway integration: Integration with secure payment gateways (PayPal,

credit cards).

• User profiles & wish lists: Profiles with saved items for future purchases

• Ratings & Reviews System: Users can review and rate products.

Release 3 (Months 5–6): Customization and Loyalty Features:

• Personalized Suggestions: Product recommendations based on user history.

• Push Alerts for Sales & Promotions: Notifications for promotions and updates.

• Integration with Loyalty Programs: Rewards for repeat purchases.

• Enhanced Security Features (e.g., 2 Step Verification): Adds 2-step verification for
account security.

2. User Stories and Backlog

a. Write five detailed user stories following the INVEST criteria (Independent,
Negotiable, Valuable, Estimable, Small, Testable).

a. Five User Stories (Following INVEST Criteria)

1. User Registration
o As a user, I want to create an account using my email or social media login so
that I can securely access my shopping account and view past purchases.
o Acceptance Criteria:
 User can register with email or social media.
 User can login/logout securely.
 User data is saved in the account.
 Confirmation email sent post-registration.
2. Product Search
o As a user, I want to search for products by name and category so that I can
find items quickly.
o Acceptance Criteria:
 Search bar is accessible from the home page.
 Results display relevant products based on search criteria.
 Search results can be filtered by price, category, and rating.
3. Shopping Cart Management

Page 2
 o As a user, I want to add and remove products from my shopping cart so that I
can manage my purchases.
o Acceptance Criteria:
 Users can add products to the cart from the product page.
 Users can view, modify, and remove items in the cart.
 Cart maintains state across sessions.
4. Checkout Process
o As a user, I want to complete my purchase in a simple and secure way so that
I can quickly finalize my transactions.
o Acceptance Criteria:
 User can review their cart before checkout.
 Payment methods are securely processed.
 Confirmation page displayed after successful purchase.
5. Order Tracking
o As a user, I want to track my order status so that I can know when to expect
delivery.
o Acceptance Criteria:
 Users receive updates via email and in-app notifications.
 Order status (e.g., processing, shipped, delivered) visible in user
account.

b. Create an initial product backlog with priority levels and estimated story points (use
T-shirt sizing or Fibonacci sequence for estimates).

User Story Priority

Story Points

User Registration & Login High 5

High 8

Product Catalog & Search

High 5

Shopping Cart
Functionality
Checkout Process High 8

Order Tracking Medium 5

Page 3
User Profiles & Wish Lists Medium 8

Payment Gateway High 13

Integration
Rating & Reviews System Medium 5

Personalized Low 8
Recommendations

Push Notifications Low 5

3. Sprint Planning
a. Plan a two-week sprint: a. Select a sprint goal aligned with the product vision.

"Implement core e-commerce functionalities that enable users to register, search for
products, manage their shopping cart, and complete the checkout process."

b. Define tasks for each user story and estimate the time required to complete them.

User Registration

 Design UI (4 hours)
 Implement backend logic (8 hours)
 Create email confirmation feature (4 hours)
 Write tests (4 hours)

Product Search

 Design UI for search (4 hours)

 Implement search functionality (8 hours)
 Develop filtering options (6 hours)
 Write tests (4 hours)

Shopping Cart Management

 Design UI for cart (4 hours)

 Implement add/remove logic (8 hours)
 Develop session management (4 hours)
 Write tests (4 hours)

Checkout Process

Page 4
  Design UI for checkout (4 hours)
 Implement payment integration (12 hours)
 Create order confirmation logic (6 hours)
 Write tests (4 hours)

Order Tracking

 Design UI for order tracking (4 hours)

 Implement tracking logic (6 hours)
 Develop notification system (6 hours)
 Write tests (4 hours)

c. Justify your selection of stories for the sprint based on priority and available team
capacity (velocity).

The selected user stories for this sprint focus on critical functionalities that form the
foundation of the mobile e-commerce experience. Each story is high priority and directly
supports the sprint goal, ensuring users can engage with the app effectively. Given the
team's capacity, assuming a velocity of 20 story points for a two-week sprint, the
estimated total of 50 points will require careful attention to ensure that we remain focused
on delivering the highest priority features within our timeline.

The focus on registration, search, cart management, and checkout will provide a
functional product for users, allowing for immediate testing and feedback, which is
essential for iterative development.

Part 2: Sprint Execution and Review

During sprint execution, assume the following conditions:

 Team Velocity: 30 story points per sprint

 Team Composition: Four developers, one tester, one ScrumMaster

1. Daily Scrum Simulation

Conduct a daily Scrum simulation. For each of the three days, document what each
team member did, will do, and any blockers encountered. Provide a log of the simulated
daily meetings.

Day 1

Team Members:

 Developer 1

Page 5
 o Did: Completed user registration UI.
o Will Do: Implement backend logic for user registration.
o Blockers: None.
 Developer 2
o Did: Worked on product search functionality; UI design completed.
o Will Do: Start implementing the search logic.
o Blockers: Waiting for input from Designer on search filters.
 Developer 3
o Did: Finished shopping cart UI and connected it to the frontend.
o Will Do: Implement add/remove logic for the cart.
o Blockers: None.
 Developer 4
o Did: Created initial design for checkout UI.
o Will Do: Begin payment integration.
o Blockers: Need confirmation on payment gateway choice from Product
Owner.
 Tester
o Did: Created test cases for user registration.
o Will Do: Start testing registration once it's implemented.
o Blockers: None.

Day 2

Team Members:

 Developer 1
o Did: Implemented backend logic for user registration.
o Will Do: Finalize testing for user registration.
o Blockers: None.
 Developer 2
o Did: Started implementing search logic.
o Will Do: Work on filtering options today.
o Blockers: Waiting for Designer on filter specifications.
 Developer 3
o Did: Implemented add/remove functionality for the shopping cart.
o Will Do: Test the cart functionality.
o Blockers: None.
 Developer 4
o Did: Began payment integration but faced issues.
o Will Do: Consult with Product Owner to clarify gateway choice.
o Blockers: Unclear specifications on payment integration.
 Tester
o Did: Tested user registration; all cases passed.
o Will Do: Start testing the shopping cart.
o Blockers: None.

Page 6
 Day 3

Team Members:

 Developer 1
o Did: Finalized user registration testing and addressed feedback.
o Will Do: Assist with shopping cart tests.
o Blockers: None.
 Developer 2
o Did: Finished implementing search filtering.
o Will Do: Work on testing search functionality.
o Blockers: None.
 Developer 3
o Did: Completed shopping cart testing; all passed.
o Will Do: Support Bob in testing search features.
o Blockers: None.
 Developer 4
o Did: Discussed payment gateway with Product Owner; got clarification.
o Will Do: Continue with payment integration.
o Blockers: None.
 Tester
o Did: Started testing search functionality.
o Will Do: Continue with search testing and provide feedback.
o Blockers: None.

2. Burndown Chart and Task Board

Create a sprint burndown chart and task board reflecting the team’s progress over a
simulated two-week sprint. Include tasks that get delayed due to dependencies.

Sprint Burndown Chart

Day Remaining story points

1 30
2 28
3 26
4 24
5 22
6 20
7 18
8 16
9 12
10 10
11 6
12 2
13 0
14 0

Page 7
 Task Board

To Do In Progress Done
User Registration UI Implementing search logic User Registration tested
Product Search UI Shopping cart logic Shopping cart tested
Payment integration Payment integration
Order Tracking UI

3. Sprint Review
Conduct a sprint review.
a. Highlight which stories were completed, and which were not.

Sprint Goal: Implement basic user registration, shopping cart functionality, and payment
gateway integration for the mobile e-commerce application.

Completed User Stories

1. User Registration: As a user, I want to be able to create an account so that I can save
my personal information.
Tasks Completed: User registration form, form validation, backend user creation API,
database integration.
2. Product Search: As a user, I want to search for products so that I can find what I need
easily.
Tasks Completed: Search bar implementation, search algorithm, product catalogue
integration, search result display.
3. Shopping cart functionality: As a user, I want to add items to my shopping cart so
that I can purchase them later.
Tasks Completed: Add to cart button, cart view, cart item management, database
integration.

Incomplete User Stories

1. Order Tracking: As a user, I want to track my order so that I can know its status and
estimated delivery time.
Tasks Incomplete: Order tracking system, integration with shipping service,
notifications for order status updates.
2. Checkout process: As a user, I want to proceed to checkout and complete my
purchase using a payment gateway.

Page 8
 Tasks Incomplete: Payment processing API integration, error handling for payment
failures, confirmation page.

b. Write a brief stakeholder feedback summary and propose any scope adjustments for
the next sprint.

Positive Feedback:
1.User Authentication: Stakeholders were pleased with the smooth user registration and
login process.
2.Product Search Functionality: The search feature was well received, with stakeholders
appreciating its accuracy and speed.

Areas for Improvement:

1.Search Result Filtering: Stakeholders suggested adding more filtering options to the
search results to help users find specific products more easily.
2.Payment Gateway Integration: There was concern over the incomplete payment
gateway integration, as this is critical for completing transactions.
3.Order Tracking: Stakeholders emphasized the importance of the order tracking feature,
noting that it is crucial for customer satisfaction.

Proposed Scope Adjustments for Next Sprint

Based on the feedback, the following adjustments are proposed for the next Sprint to
address stakeholder concerns and improve the application:
1.Complete Payment Gateway Integration:
Tasks: Finalize the payment processing API integration, implement error handling for
payment failures, and design the payment confirmation page.
Priority: High, as this functionality is essential for the e-commerce application to process
transactions.
2.Enhance Order Tracking Feature:
Tasks: Develop the order tracking system, integrate with the shipping service, and
implement notifications for order status updates.
Priority: High, to improve user experience and satisfaction.
3.Improve Search Result Filtering:
Tasks: Add filtering options such as price range, category, and user ratings to the search
results.
Priority: Medium, to enhance usability and help users find products more efficiently.
4.Increase Automated Testing Coverage:
Tasks: Implement additional unit tests for search functionality, payment processing, and
order tracking.
Priority: Medium, to ensure reliability and detect issues early.

Page 9
 5.Design Refinements:
Tasks: Refine the visual design of the cart summary based on stakeholder feedback to
make it more user-friendly.
Priority: Medium, to improve user interface and overall experience.

4. Sprint Retrospective
Start

1. Regular Code Reviews

Action: Implement scheduled code review sessions twice a week.

Improvement: Regular code reviews will help catch bugs and improve code quality early,
fostering a culture of continuous learning and ensuring adherence to coding standards.

2.Automated Testing

Action: Increase the use of automated tests for new features.

Improvement: Automated testing will help catch regressions early, ensure new code is
reliable, and reduce manual testing efforts, leading to a more efficient development
process.

Stop

1. Multitasking

Action: Avoid working on multiple user stories simultaneously.

Improvement: Focusing on one user story at a time will reduce context switching,
increase efficiency, and ensure higher quality outcomes for each completed story.

2. Ad-hoc Meetings

Action: Minimise unscheduled, ad-hoc meetings and stick to planned Scrum ceremonies.

Improvement: Reducing interruptions will help maintain workflow continuity and allow
team members to focus better on their tasks, leading to higher productivity.

3. Neglecting Retrospective Actions

Action: Ensure all action items from retrospectives are tracked and implemented in
subsequent sprints.

Page 10
 Improvement: Addressing and acting on retrospective action items will continuously
improve processes and team performance, fostering a culture of accountability and
growth.

Continue

1.Daily Stand-ups

Action: Maintain daily stand-ups to ensure clear communication.

Improvement: Daily stand-ups help in quickly identifying and resolving blockers,

promoting transparency and keeping the team aligned with sprint goals.

2.User Feedback Integration

Action: Continue integrating user feedback into the product backlog.

Improvement: Regularly incorporating user feedback ensures that the product meets user
needs and expectations, improving user satisfaction and product relevance.

3.Clear Sprint Goals

Action: Keep defining clear and achievable sprint goals.

Improvement: Having well-defined sprint goals helps the team stay focused, motivated,
and aligned, ensuring that each sprint delivers meaningful progress toward the overall
product vision.

How These Actions Will Improve the Next Sprint

4.Enhanced Quality: Regular code reviews, pair programming, and automated testing
will improve the overall quality of the codebase, leading to fewer bugs and more robust
features.

Increased Focus: By stopping multitasking and minimising ad-hoc meetings, team

members can focus better on their tasks, leading to higher efficiency and productivity.

5. Continuous Improvement: Tracking and implementing retrospective action items

will ensure continuous process improvements, leading to a more effective and cohesive
team.

6.Better Communication: Maintaining daily stand-ups and clear sprint goals will
enhance communication and alignment within the team, ensuring everyone is on the same
page and working toward common objectives.

Part 3: Metrics, Flow, and Communication

Page 11
 1. Agile Metrics Analysis
a. Analyze the team’s velocity trend over three sprints (including the simulated sprint).
Identify any inconsistencies and propose solutions for more accurate estimation and task
breakdown.

Velocity Data Over Three Sprints:

Sprint Completed Story Points

Sprint 1 28
Sprint 2 30
Sprint 3 (Simulated) 24

Analysis:

Trend Observation:

The team's velocity increased between Sprints 1 and 2, indicating improved efficiency
and productivity. However, a subsequent decrease in Sprint 3 points to potential
obstacles, such as complex tasks or external factors that may have hindered progress.

Inconsistencies:

The decline in velocity in Sprint 3 may be linked to difficulties encountered while

implementing new features, specifically payment integration. Furthermore, unforeseen
bugs that required additional time for resolution could have impacted the team's progress.
Additionally, variations in team capacity due to factors like vacations or unexpected
absences might have contributed to the decrease.

Proposed Solutions:

1. Enhance Task Estimation and Prioritization:

 Regular Calibration Sessions: Conduct regular calibration sessions to ensure

consistent story point estimation.
 Detailed Task Breakdown: Break down large tasks into smaller, more manageable
subtasks.
 Prioritization Techniques: Employ effective prioritization techniques, such as
MoSCoW or RICE, to focus on high-value tasks.

2. Improve Team Capacity Planning:

 Proactive Resource Allocation: Plan for potential capacity fluctuations, such as

vacations or sick leave.
 Flexible Work Arrangements: Consider flexible work arrangements to
accommodate personal commitments.

Page 12
  Cross-Functional Collaboration: Foster collaboration between team members to
share knowledge and support each other.

3. Enhance Technical Practices:

 Continuous Integration and Continuous Delivery (CI/CD): Implement CI/CD

pipelines to automate testing and deployment processes.
 Test Automation: Automate tests to reduce manual effort and accelerate feedback
cycles.
 Code Reviews: Conduct regular code reviews to maintain code quality and identify
potential issues early.

4. Strengthen Communication and Collaboration:

 Effective Communication Channels: Use appropriate communication channels

(e.g., Slack, Teams, or project management tools) to facilitate information sharing.
 Regular Stand-ups and Retrospectives: Conduct regular stand-up meetings and
retrospectives to address issues and improve team collaboration.
 Transparent Communication: Encourage open and honest communication between
team members and stakeholders.

5. Address Technical Debt:

 Prioritize Technical Debt: Identify and prioritize technical debt items based on their
impact on future development.
 Allocate Time for Refactoring: Schedule dedicated time for refactoring and code
improvement.
 Learn from Mistakes: Analyze past mistakes to avoid similar issues in the future.

By implementing these solutions and continuously monitoring the team's performance,

the team can improve its velocity, reduce the impact of unforeseen challenges, and
deliver higher-quality software.

b. Evaluate the defect rate and lead time to assess product quality and team
performance. Suggest two ways to improve product quality in future sprints.

Defect Rate and Lead Time:

Defect Rate

 Current Rate: 1.67 defects per sprint

 Interpretation: A high defect rate indicates potential quality issues, such as
insufficient testing, lack of code reviews, or inadequate requirements gathering. This

Page 13
 defect rate suggests a moderate level of quality issues. While it's not alarmingly high,
it indicates room for improvement.

Lead Time

Current Trend: Increased from 6 days to 8 days in the last sprint

 Interpretation: A long lead time can signal bottlenecks in the development process,
such as slow build times, lengthy testing cycles, or complex deployment procedures.
It could be due to increased complexity, resource constraints, or inadequate task
prioritization.

Evaluation:

Regarding Defect Rate:

 Root Cause Analysis: Conduct a thorough analysis of the root causes of defects to
identify trends and patterns. This can help in implementing targeted preventive
measures.
 Defect Prevention Strategies: Proactively address potential defect sources through
techniques like pair programming, code reviews, and static analysis tools.

Regarding Lead Time:

 Bottleneck Identification: Use tools like Kanban boards or flow metrics to pinpoint
the specific stages causing delays in the workflow.
 Task Prioritization: Ensure that tasks are prioritized effectively to avoid
unnecessary delays and resource contention.
 Efficient Task Assignment: Optimize task assignment to balance workloads and
leverage team members' strengths.
 Continuous Improvement: Regularly review and refine the development process to
identify and eliminate inefficiencies.

Suggestions for Improving Product Quality:

1. Automate the Development Process: Implement a Continuous

Integration/Continuous Deployment (CI/CD) pipeline to automate the building,
testing, and deployment of code. This will significantly reduce lead times and
improve the overall quality of the product by catching and fixing defects early in the
development cycle.
2. Learn from Mistakes: Conduct regular retrospectives to analyze past mistakes,
identify the root causes of defects, and discuss lessons learned. This will help the
team to adapt their processes, tools, and practices to prevent similar issues from
recurring in future sprints.

Page 14
 2. Task Flow Management
Simulate a scenario where tasks are getting stuck in "In Progress" due to unresolved
dependencies. Propose a flow management strategy that includes swarming, limiting
WIP, and effective communication to resolve the issue.

Scenario Simulation

Scenario: Tasks Stuck in "In Progress" Due to Unresolved Dependencies

Problem: A team is facing a common issue where tasks are getting stuck in the "In
Progress" state because of unresolved dependencies. This leads to delayed task
completion, increased lead time, and reduced overall productivity.

Proposed Flow Management Strategy:

To address this issue, we propose a combined strategy involving swarming, limiting

Work-In-Progress (WIP), and effective communication:

1. Swarming Technique:

 Identify Bottlenecks: Pinpoint the specific tasks or team members that are causing the
dependencies and delays.
 Form a Swarming Team: Assemble a team of skilled individuals to focus on resolving
the dependencies and completing the stuck tasks.
 Collaborative Problem-Solving: The team should work together to identify and
eliminate roadblocks, brainstorm solutions, and provide support to each other.
 Time-boxed Sessions: Set specific time limits for swarming sessions to maintain
focus and avoid unproductive discussions.

2. Limit Work-In-Progress (WIP):

 Kanban Board: Use a Kanban board to visualize the workflow and limit the number
of tasks in progress at any given time.
 WIP Limits: Set clear WIP limits for each stage of the workflow to prevent
overloading team members and reduce the risk of context switching.
 Focus on Completion: Encourage the team to prioritize task completion and avoid
starting new tasks until existing ones are finished.

3. Effective Communication:

 Regular Stand-ups: Conduct daily stand-up meetings to discuss progress, blockers,

and dependencies.
 Transparent Communication: Ensure open and honest communication among team
members to identify and resolve issues promptly.

Page 15
  Visualize Dependencies: Use tools like dependency maps or mind maps to visualize
the relationships between tasks and identify potential bottlenecks.
 Proactive Communication: Keep stakeholders informed about the status of tasks and
any potential delays.

3. Information Radiator & Communication

Design an information radiator (e.g., task board, burndown chart) that will help the
team and stakeholders track sprint progress in real-time. Explain how it improves team
communication and transparency.

Information Radiator Design

Components:

1. Task Board:
o Columns for "To Do," "In Progress," "Blocked," and "Done." Each task
includes the assignee and estimated story points.
o Colour coding for priority (e.g., red for high priority, yellow for medium).

2. Burndown Chart:
o A line chart showing the remaining story points daily. It indicates whether the
team is on track to complete the sprint within the designated time.

Page 16
 3. Defect Dashboard:
o A visual representation of defects categorized by severity and status (e.g.,
open, in progress, resolved). This helps the team track and manage product
quality actively.

Page 17
 How It Improves Communication and Transparency

 Visibility: Team members and stakeholders have real-time access to progress,

allowing for quick identification of issues or delays.
 Alignment: The visual layout fosters discussions about priorities and focuses on
collaborative problem-solving, ensuring everyone is aware of the current sprint's
status.
 Engagement: By keeping stakeholders informed, it promotes trust and collaboration,
making them feel more involved in the product development process.

By leveraging these strategies and tools, the team can enhance their workflow, improve
communication, and maintain a steady pace toward delivering a high-quality mobile e-
commerce application.

Page 18