Scrum methodology
Upcoming SlideShare
Loading in...5
×

Like this? Share it with your network

Share

Scrum methodology

  • 219 views
Uploaded on

A Brief presentation introducing SCRUM in software development

A Brief presentation introducing SCRUM in software development

More in: Technology , Business
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Be the first to comment
    Be the first to like this
No Downloads

Views

Total Views
219
On Slideshare
219
From Embeds
0
Number of Embeds
0

Actions

Shares
Downloads
4
Comments
0
Likes
0

Embeds 0

No embeds

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
    No notes for slide

Transcript

  • 1. Empirical Process Control
  • 2.
    • An Agile Development Methodology
    • Introduces the empirical process control idea
    • Projects divided into succinct work cadences, known as sprints.
    • At the end of each sprint stakeholders and team members meet to assess the progress of a project and plan its next steps.
  • 3.
    • Product Owner
      • Communicates the vision
      • Represents the customer requirements
    • Scrum Master
      • Liaison between Product Owner and Team
      • Does not manage the team
      • Helps the team remain creative and productive
      • Advises Product Owner about ROI
  • 4.
    • Team Member
      • Responsible for completing the work
      • 7 cross-functional members
      • Mix of software engineers, architects, programmers, analysts, QA experts, testers, and UI designers.
      • For each sprint the team determines how and when it will be done.
      • This imposes great responsibility.
  • 5.  
  • 6.  
  • 7.
    • Helps the company in saving time and money.
    • Fast moving developments can be coded and tested and mistakes can be easily rectified.
    • Easier to cope with changes.
    • Easier to deliver a quality product in a scheduled time.
    • enables project’s where the business requirements documentation is hard to quantify.
  • 8.
    • If team members are not committed, the project will either never complete or fail.
    • It works well only with small teams and projects
    • Needs experienced team members only
    • Absence of a team member during development can have huge inverse effect on the project development
    • Project quality management is hard to implement and quantify unless the test team are able to conduct regression testing after each sprint.
  • 9.