Your SlideShare is downloading. ×
0
Empirical Process Control
<ul><li>An Agile Development Methodology </li></ul><ul><li>Introduces the empirical process control idea </li></ul><ul><li...
<ul><li>Product Owner </li></ul><ul><ul><li>Communicates the vision </li></ul></ul><ul><ul><li>Represents the customer req...
<ul><li>Team Member </li></ul><ul><ul><li>Responsible for completing the work </li></ul></ul><ul><ul><li>7 cross-functiona...
 
 
<ul><li>Helps the company in saving time and money.  </li></ul><ul><li>Fast moving developments can be coded and tested an...
<ul><li>If team members are not committed, the project will either never complete or fail. </li></ul><ul><li>It works well...
 
Upcoming SlideShare
Loading in...5
×

Scrum methodology

160

Published on

A Brief presentation introducing SCRUM in software development

Published in: Technology, Business
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
160
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
5
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Transcript of "Scrum methodology"

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

    Clipping is a handy way to collect important slides you want to go back to later.

×