13.32M

Категория:

Программное обеспечение

Software development life cycle

Software Development Methodologies
• Waterfall Model
• Joint Application Development
• Prototype Methodology
Methodology
• Agile Methodology
• Lean Development Methodology
• Rapid Application Development • Rational Unified Process
• Dynamic System Development
Methodology
Model Methodology
• Scrum Development Methodology
• Spiral Model
• Extreme Programing Methodology

4.

Which methodology is better?

5.

8 planning principles
which makes your life easier

6.

1.
Estimation should be done by team
not manager

7.

2. Plan the time when product will be released

8.

3. Project splits to small chunks with clear
aims and result discussions

9.

4. Close team collaboration

10.

5. Add some buffer time

11.

6. Don’t hurry up or cut time for development

12.

7. Document your plan using some tool

13.

8. Put priorities and concentrate on the main

14.

15.

Software development methodology
In software engineering, a software development methodology
is a division of software development work into distinct phases (or
stages) containing activities with the intent of better planning and
management.

16.

17.

18.

19.

20.

The Scrum Team
• The Product Owner
• The Development Team
• The Scrum Master

21.

The Product Owner
• Ordering the items in the Product Backlog to best achieve
goals and missions
• Ensuring that the Product Backlog is visible, transparent, and
clear to all, and shows what the Scrum Team will work on next
• The Product Owner is one person

22.

The Development Team
Self-organizing
Cross-functional
Scrum recognizes no sub-teams
Accountability belongs to the whole team
No less than 3, not bigger than 9

23.

The Scrum Master
Scrum Master Service to the Product Owner
• Finding techniques for effective Product Backlog management;
• Helping the Scrum Team understand the need for clear and
concise Product Backlog items;
• Ensuring the Product Owner knows how to arrange the
Product Backlog to maximize value;
• Facilitating Scrum events as requested or needed.

24.

The Scrum Master
Scrum Master Service to the Development Team
• Coaching the Development Team in self-organization and
cross-functionality;
• Removing impediments to the Development Team’s progress;
• Facilitating Scrum events as requested or needed;
• Coaching the Development Team in organizational
environments in which Scrum is not yet fully adopted and
understood

25.

The Scrum Master
Scrum Master Service to the Organization
• Leading and coaching the organization in its Scrum adoption;
• Planning Scrum implementations within the organization;
• Working with other Scrum Masters to increase the
effectiveness of the application of Scrum in the organization.

26.

Meeting
Planning Meeting
Daily Standup Meeting
o What is a Product Backlog?
o Daily 15 minutes
o What can we do?
o Issues:
o Further details?
o What have I done?
o Who will do it?
o What will I do?
o How long will it take?
o What is my problem?
Sprint Review
o For the Product
Owner
Sprint Retrospective
o Analysis of the work
done
o For the customers. o At the end of sprint
o At the end of each
sprint

27.

Burn Down Chart

28.

• https://www.youtube.com/watch?v=502
ILHjX9EE

29.

Waterfall

30.

Waterfall
Pros:
• Simple and easy to understand and use
• Easy to manage due to the rigidity of the model
• Phases are processed and completed one at a time
• Works well for smaller projects where requirements are very well
understood
• Process and results are well documented

31.

Waterfall
Cons:
• No working software is produced until late during the life cycle.
• High amounts of risk and uncertainty.
• Poor model for long and ongoing projects.
• Not suitable for the projects where requirements are at a
moderate to high risk of changing
• It is difficult to measure progress within stages.

32.

Prototype Methodology

33.

Prototype Methodology
Pros:
• Gives clear idea about the functional process
of the software
• Reduces the risk of failure in a software
functionality
• Assists well in requirement gathering and the
overall analysis

34.

Prototype Methodology
Cons:
• Chances of extension in management cost
• Excessive involvement of client can affect
processing
• Too many changes affect the workflow of the
software

35.

36.

Rational Unified Process Methodology (RUP)

37.

Rational Unified Process Methodology (RUP)
• More than 30 roles
• More than 20 events
• More than 70 artifacts

38.

Rational Unified Process Methodology (RUP)
Pros:
• Lays high focus on precise documentation
• Removes project risks linked with client
evolving needs
• Very less requirement for integration

39.

Rational Unified Process Methodology (RUP)
Cons:
• Needs excessively expert software developer
• Development procedure of the methodology is complicated
• Integration might cause confusion
• Very complicated to understand

40.

Extreme Programing Methodology (XP)
It is chiefly used for crafting software within a very unbalanced atmosphere.

41.

Extreme Programing Methodology (XP)
Pros:
• It lays focus on customer involvement
• Establishes rational plans and schedules
• Developers are exceptionally committed to the project
• Equipped with modernistic methods for quality software

42.

Extreme Programing Methodology (XP)
Cons:
• Effectiveness depends on the people involved
• Requires frequent meeting for development raising total costs
• Necessitates for excessive development changes
• Exact possibilities and future outcomes are really unknown

43.

Scaled Agile Framework (SAFe)
http://www.scaledagileframework.com

44.

Lean Development Methodology

45.

Lean Development Methodology
• Pros:
• Lower budget & time requirements
• Allows for delivery of product early

46.

Lean Development Methodology
Cons
• The workability of the team decides success of software
development process
• Unsuitable business analyst can be severely problematic
• Excessive flexibility leads developer to lose focus

47.

Kanban
Release when you want or ready
Now time limit as Iterations
Column as many as you need. (Less is better)
Watch out for traffic jams in columns
Kanban board not cleares each iterations as Scrum board
Kanban board can have tasks with different estimation (1 day, 1
month)

48.

Kanban
• For better estimation split tasks to equal parts
• Swim lanes
• Spent 20% of time for support and 80% for new functionality

49.

Scrumban
We can add PO to kanban
Or few minutes sunc up (stand up)
When you add limit for stories on Scrum board
Teams start with scrum than understand that it’s not a good
practice having a lot in progress
• In kanban people try to estimate tasks as in scrum
• When in scrum people want to have iteration less than week or
cancel iterations at all.