3. WATERFALL - basically is a sequential model where software development is segregated into a sequence
of pre -defined phases, where each phase depends on the deliverables of the previous one and
corresponds to a specialisation of tasks.
CONS'
- Absence of flexibility
- It is required to design and describe the final
product in the initial project stage
- Absence of incurring the essential changes in
the process of development
- Huge considerable amount of time "go-to-the-
market"
WATERFALL
CONCEPTION DEPLOYMENT
INITIATION
ANALYSIS
DESIGN
CONSTRUCTION
TESTING
4. AGILE
Agile is an iterative, team-based approach to development.
This approach emphasizes the rapid delivery of an
application in complete functional components. Rather than
creating tasks and schedules, all time is “time-boxed” into
phases called “sprints.”
VALUABLES
- People & relationships are more important than processes and instruments
- Working Product is more important than massive document flow
- Collaboration with the customer is more important than negotiation the terms of the contract
- Preparedness for the changes is more important than sticking to the initial roadmap of the
product
https://agilemanifesto.org/iso/ru/manifesto.html
5. 12
PRINCIPLES
OF AGILE
12Principlesarebasedonthe AgileManifestoTO SATISFY THE CUSTOMER THROUGH EARLY AND
CONTINUOUS DELIVERY OF VALUABLE SOFTWARE
WELCOME CHANGING REQUIREMENTS
DELIVER WORKING SOFTWARE FREQUENTLY
BUSINESS PEOPLE AND DEVELOPERS MUST WORK
TOGETHER DAILY THROUGHOUT THE PROJECT
BUILD PROJECTS AROUND MOTIVATED INDIVIDUALS
THE MOST EFFICIENT AND EFFECTIVE METHOD OF
CONVEYING INFORMATION - F2F TALKS
WORKING SOFTWARE IS THE PRIMARY MEASURE OF
PROGRESS
AGILE PROCESSES PROMOTE SUSTAINABLE DEVELOPMENT
CONTINUOUS ATTENTION TO TECHNICAL EXCELLENCE AND
GOOD DESIGN ENHANCES AGILITY
SIMPLICITY–THE ART OF MAXIMIZING THE AMOUNT OF
WORK NOT DONE–IS ESSENTIAL
THE BEST ARCHITECTURES, REQUIREMENTS, AND DESIGNS
EMERGE FROM SELF-ORGANIZING TEAMS
AT REGULAR INTERVALS, THE TEAM REFLECTS ON HOW TO
BECOME MORE EFFECTIVE, THEN TUNES AND ADJUSTS ITS
BEHAVIOR ACCORDINGLY
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
11.
12.
6. SCRUM VS.
KANBAN
The main difference between Scrum and
Kanban is in the length of iterations. In Scrum
iteration - 2 weeks, in Kanban the developer
executes the tasks stepwise
7. SCRUM
SCRUM - agile software development
methodology based on principles of AGILE,
divided into SPRINTS, users will receive the
better & improved product.
Product Owner
Scrum Master
Team:developer, designer,
analytic
ROLES IN SCRUM
8. 01
Scrum-master is one of the roles in Scrum. Scrum Master is in
charge of the success of the Scrum in the project by uniting
management and development.
The responsibilities of the Scrum-master:
- Supports the unity of the Team
- Maintains the transparency and the collaboration
- Eliminates the obstacles, that impedes the effectiveness of the
project team
- Maintains the Agile & Scrum valuables (helps others to perceive the
valuables of the Scrum)
- If required - protects the Development Team
- Facilitates the Scrum-conference calls/meet-ups
- Aids the Team and increases the effectiveness of it
Who is Scrum
Master?
Product Owner
Development Team
Organization
Services:
1.
2.
3.
9. Artifacts of Scrum -
elements that are
required for the team
in order to achieve
the results.
ScrumArtificats!NKLN
Essentials
-Product Backlog
-Sprint Backlog
Burdndown chart
Increment
Additional
-DoD - Definition of Done
-DoR - Definition of Ready
- Story Points
- Product Board
