Assignment 5
Agile Project Simulation
Dinara Amangeldi, Zhanel Mukhtarova, Aidana Tugelbai, Aidana Zhamiyeva
Group: ITM-2203
Department of IT Management, Astana IT University
Agile Management in Virtual Environments
Symbat Issabayeva
November 7, 2024
Table of contents
1. Introduction.....................................................................................................................................................
2. Sprint Planning...............................................................................................................................................
User Stories.....................................................................................................................................................
Prioritization....................................................................................................................................................
Task Breakdown.............................................................................................................................................
3. Sprint Execution Simulation..........................................................................................................................
Team and Task Assignment:.....................................................................................................................
Brief Progress Discussion.........................................................................................................................
Sprint Wrap-up..........................................................................................................................................
4. Sprint Retrospective.......................................................................................................................................
5. Conclusion........................................................................................................................................................
2
1. Introduction
Our project aims to develop an engaging, interactive mobile application to support
learners in studying the Kazakh language and deepening their understanding of Kazakh
culture. This platform combines modern educational techniques with cultural insights to
create a holistic learning experience. Key features include:
●Mobile App Development: The application will offer interactive lessons and quizzes
designed to make language learning accessible and enjoyable.
●Cultural Insights: Beyond language, the platform will introduce users to Kazakh
customs, traditions, and history, fostering a deeper appreciation for the culture.
●Gamification: To maintain user engagement and motivation, we’ll incorporate
gamified elements like badges, levels, and rewards for milestones achieved.
●Progress Tracking and Personalised Learning: Users will be able to track their
progress, with personalised recommendations tailored to their strengths and areas for
improvement.
By offering an immersive experience, this digital platform will not only promote
Kazakh language skills but also encourage a greater understanding and appreciation of
Kazakh culture.
Link to the Miro Board: Miro Board
3
4
2. Sprint Planning
User Stories
User Activity: Registration and Authorisation
● User Story: As a user, I want to create an account in the app so that I can save my
achievements and track my progress.
● User Story: As a user, I want to log in to the app to continue learning from where I
left off.
User Activity: Selecting a Proficiency Level
● User Story: As a new user, I want to take a placement test to determine my
proficiency level so that the app can suggest suitable lessons and tasks.
User Activity: Taking Lessons
● User Story: As a user, I want access to various lessons with audio, texts, and videos so
that I can learn Kazakh at different levels of difficulty.
● User Story: As a user, I want to see examples of dialogues and phrases in Kazakh so
that I can better understand how the language is used in real-life situations.
User Activity: Completing Exercises
● User Story: As a user, I want to complete exercises after each lesson to check my
understanding of the material.
● User Story: As a user, I want to receive feedback on my exercise results so that I can
understand my mistakes and improve my skills.
5
User Activity: Pronunciation Practice
● User Story: As a user, I want the ability to record my pronunciation and compare it
with native speakers so that I can improve my pronunciation in Kazakh.
User Activity: Gamification and Rewards
● User Story: As a user, I want to earn points and rewards for completing lessons and
exercises to feel motivated to continue learning.
● User Story: As a user, I want to track my progress through achievements or levels so
that I can see how my skills improve over time.
User Activity: Reminders and Goals Setting
● User Story: As a user, I want to set daily goals for language learning to organise my
study schedule.
● User Story: As a user, I want to receive reminders to complete lessons or exercises so
that I don’t forget to practice the language.
User Activity: Access to additional materials
● User Story: As a user, I want access to articles, videos, and audio materials about
Kazakh culture so that I can deepen my immersion in the language and its cultural
context.
Prioritization
MoSCoW method
● Must have - red
● Should have - purple
6
● Could have - blue
● Won't have - grey
Task Breakdown
1. Registration and Login
Tasks
● Create user registration form – 3 story points
● Implement email/password validation – 2 story points
● Set up backend for account storage – 5 story points
● Develop login form and session handling – 3 story points
● Set up password recovery process – 3 story points
Total Estimated Points: 16 story points
2. Selecting a Proficiency Level
Tasks
● Design proficiency level test questions – 4 story points
● Implement test interface (UI) – 3 story points
● Set up logic to analyze test results and determine level – 5 story points
● Develop backend to store test results – 3 story points
● Integrate test result data with lesson suggestions – 4 story points
Total Estimated Points: 19 story points
3. Taking Lessons
7
Tasks
● Develop lesson content structure (audio, text, video) – 5 story points
● Create lesson UI for lesson navigation and display – 4 story points
● Integrate lesson content with user progress tracking – 4 story points
● Develop audio and video player for lessons – 5 story points
● Create backend for lesson storage and retrieval – 3 story points
Total Estimated Points: 21 story points
8
9
10
3. Sprint Execution Simulation
Team and Task Assignment:
1. Aidana Zhamiyeva (Backend Developer)
○ Task: Set up the backend to handle lesson data storage, user
progress tracking, and create API endpoints for data retrieval.
○ Expected Deliverables: Functional backend structure and API to
support content delivery and user progress tracking.
2. Dinara Amangeldi (Content Creator)
○ Task: Develop content for the Basic Vocabulary Module,
focusing on everyday phrases, greetings, and essential vocabulary.
○ Expected Deliverables: Content for 10 lessons with phrases and
practice exercises for vocabulary building.
3. Aidana Tugelbai (UI/UX Designer)
○ Task: Design interfaces for Lesson Overview, Interactive
Exercises, and Progress Tracking screens.
○ Expected Deliverables: Initial wireframes for user testing,
optimized for easy navigation and engagement.
4. Zhanel Mukhtarova (Frontend Developer)
○ Task: Implement the lesson and exercise screens using the
designs, connecting to backend APIs for dynamic content loading.
○ Expected Deliverables: Functional front-end that displays lessons,
exercises, and tracks progress interactively.
Brief Progress Discussion
11
1. Айдана Жамиева (Backend Developer): Backend structure and API endpoints
are set up and functional, with some optimization still needed.
2. Динара Амангельди (Content Creator): Initial vocabulary and phrases for five
lessons completed. Feedback shows users appreciate context-based phrases, so
additional examples will be added.
3. Айдана Тугельбай (UI/UX Designer): Wireframes completed, with initial
testing indicating the need for simpler navigation. Working on updates to improve
flow.
4. Жанель Мухтарова (Frontend Developer): Basic layout of lesson and exercise
screens completed; next steps involve linking screens to backend data for interactive
use.
Sprint Wrap-up
● Outlook for Next Sprint: Integrate front-end and back-end fully, ensuring
seamless data flow and functionality for a basic but operational learning module.
12
4. Sprint Retrospective
What Went Well
● Efficient Collaboration
Communication among team members was seamless. Regular check-ins helped us
stay aligned and address issues quickly.
● Task Prioritization
The MoSCoW prioritization helped us focus on the “Must Have” tasks, keeping the
scope manageable and on track.
● Proficiency Level Test
We successfully implemented the logic for the proficiency test and connected it with
lesson suggestions without major issues.
● User Authentication
Registration and login were completed smoothly, with minimal bugs, and the
feedback from testing was positive.
13
What Could Be Improved
● Time Management on UI Tasks
UI development took longer than expected. We underestimated the time needed for
creating a responsive and accessible user interface.
● Better Handling of Unforeseen Technical Challenges
We encountered unexpected technical challenges with the proficiency level test logic,
which took more time than anticipated. A risk assessment could have helped prepare
for these issues.
● Improved Task Distribution
A few developers had a heavier workload than others. Redistributing tasks more
evenly could help keep everyone’s pace steady and prevent bottlenecks.
● Time Allocation for Research and Learning
Some developers expressed the need for more time to research new tools and
techniques that could enhance our development process. This is especially important
for evolving technologies that could impact our project.
Action items
● Improve Time Estimates for UI Tasks
Re-evaluate time estimates for UI tasks in the next planning session. Include a buffer
for design and testing time.
● Implement Risk Assessment Procedures
Establish a process for identifying potential technical challenges during sprint
planning. Develop a risk log to document risks and determine mitigation strategies,
particularly for complex tasks like the proficiency level test.
14
● Balance Task Distribution
Review the current workload of each team member during sprint planning. Utilize a
task allocation tool to ensure that tasks are evenly distributed and adjust assignments
as necessary throughout the sprint.
● Regular Check-ins for Technical Tasks
Schedule brief technical check-ins during the sprint for complex tasks, allowing team
members to discuss progress, share insights, and address challenges in real-time.
● Feedback Loop for Continuous Improvement
Create a feedback mechanism after each sprint where team members can share
insights about the process and suggest improvements. This will help identify recurring
issues and foster a culture of continuous improvement.
15
16
5. Conclusion
Our sprint planning exercise offered hands-on experience in Agile methodology,
deepening our understanding of effective teamwork and project organisation. By using the
MoSCoW approach to prioritise tasks, we learned to focus on developing a minimum viable
product (MVP) that delivers the most value to users. The exercise highlighted how clear
communication and well-defined roles are crucial for maintaining workflow and meeting
deadlines.
Throughout the sprint, each team member contributed unique skills, reinforcing the
importance of cross-functional collaboration in Agile. The retrospective session was
particularly insightful, allowing us to identify specific areas for improvement, such as
enhancing our story point estimation for better task sizing and refining our task allocation to
avoid bottlenecks.
Overall, this experience not only solidified our knowledge of Agile principles but also
strengthened our skills in adapting these principles to real-world projects. These lessons in
prioritisation, task management, and iterative feedback will serve us well in future projects,
enabling us to deliver more efficiently and collaboratively.
17