ПП_6_Детальное_планирование_и_оценка_1

1.

Project Practicum
Detailed planning and evaluation

2.

Decomposition
The problem with complex projects:
● Cognitive overload when working on large tasks
● Unpredictability of deadlines and resources
● Vague completion criteria
● Difficulty coordinating between participants
Objectives of decomposition:
● Reduce cognitive load through step-by-step implementation
● Increase the accuracy of planning and estimation
● Clearly define the boundaries and criteria for task completion
● Improve project transparency and manageability

3.

Steps Agile
Stage 1 – Epic
● A large, business-focused system module
● Characteristics:
● Covers a cross-cutting business function
● Implemented in 2-4 sprints
● Involves multiple user roles
● Has measurable business metrics
● Formulation: [Action] + [Object] + [Context]
Examples:
● "Implementation of an authentication and authorization system"
● "Creation of a user data management module"
● "Development of an admin panel"

4.

Steps Agile
Stage 2 – User Story
A specific feature from the end user's perspective
Formulate:
As a [<user type>], I want to [<perform an action>]
in order to [<receive a benefit>]
Example:
As a registered user, I want to change the email
address in my profile to use up-to-date contact
information
INVEST-quality criteria:
Independent – Независимая
Negotiable - Обсуждаемая
Valuable – Ценная для юзера
Estimable – Оцениваемая
Small – Небольшая
Testable – Тестируемая

5.

Steps Agile
Stage 3 – Task
● Specific technical work for implementing the story
● Task types:
● Development (Frontend, Backend, API)
● Design (UI/UX, interface design)
● Testing (Unit tests, integration testing)
● Documentation (technical, user)
● Infrastructure (environment setup, deployment)

6.

Steps Agile
Stage 3 – Task
● Examples for changing email:
● "Create an API endpoint for changing email"
● "Develop a frontend form with validation"
● "Write unit tests to verify business logic"
● "Implement email notification sending"
● Task Requirements:
● Complete in 1-2 days
● Assigned to one performer
● Has clear completion criteria
● Can be verified and tested

7.

Story Points Evaluation Methodology
Three-factor estimation model:
Work volume - the amount of effort required
Complexity - the technical and architectural complexity
Uncertainty - the degree of unknown factors
Fibonacci sequence in estimations:
1, 2, 3, 5, 8, 13, 21, 34, 55, 89

8.

Process Planning Poker
User Story Review
Individual Estimation by All Participants
Simultaneous Reveal of Cards
Discussion of Estimate Differences
Iteration until Consensus is Reached
Benefits of this Approach:
Collective Decision Making
Early Identification of Hidden Complexities
A Shared Understanding of Requirements by the Team

9.

Hometask
* Use the reasons you've already identified using the Ishikawa Diagram or MindMap (except those
you've already used).
Select 3 reasons from your Ishikawa Diagram/MindMap.
Turn each reason into a User Story. Formulate 3 separate USs that solve these problems.
Example:
Reason: "No deadline notifications" -> US: "As a student, I want to receive push notifications 24
hours before an assignment deadline so I don't forget."
Reason: "The file upload interface is inconvenient." -> US: "As a user, I want to drag and drop files
into the browser window to upload them, making it faster and more convenient."
Reason: "The scoring system is unclear." -> US: "As a student, I want to see a visual chart of my
current course scores so I can understand my progress."
For each User Story, decompose it into Tasks.