Evolution of Agile scrum software development methodology for software industryBy: Abdullah Raza LakhanB08MEIT21

Supervisor Prof. Dr. Muhammad Akram Shaikh Co-Supervisor Assistant Professor Naveed Ahmed Jaffari

AGENDA What is Agile Scrum? Life Cycle of Agile Scrum Characteristics of scrum Component of Scrum

i. Roles of Scrum Problem statement Goal Case Study Results Conclusion References

INTRO OF AGILE SCRUM Scrum is a development methodology commonly used to oversee projects. Below figure represent agile example.

LIFE CYCLE OF SCRUM

CHARACTERISTICS Self-organizing teams

Product progresses in a series of two- to- four-week “sprints”

Requirements are captured as items in a list of “product backlog”

Uses generative rules to create an agile environment for delivering projects

COMPONENT OF SCRUM ROLES Product Owner Scrum master Team The Product Owner (typically someone from a

Marketing role or a key user in internal development) prioritizes the Product Backlog.

The Scrum Master is responsible for making sure a Scrum team lives by the values and practices of Scrum.

Scrum teams do not include any of the Traditional software engineering roles such as Programmer, Designer, Tester, or Architect. Everyone on the project works together to complete the set of work, they have collectively committed to complete within a sprint.

PROBLEM STATEMENT In traditional methodology Some vital changes are

being made in project feel difficulty, and during an application in the testing Stage, it is very difficult to go back and do some eminent changes. One may Go to come across large projects with expensive cost.

Customer not involvement during any phase. To Change the mind for changing requirement in SRS

is so difficult after project has been started. After project execution Customer satisfaction is less

than expected. Tradition methodology Continuous planning for project

is the biggest problem. Finding Bugs at the end of implementaion is blending

then re-write code again from starting.

GOAL All problems occurring during traditional

methodology phases are fixed using Case study on (shopping cart) project with agile scrum methodology.

LIFE CYCLE OF CASE STUDY CONTAINS FOLLOWING STEPS Product Backlog. Sprint Planning Meeting. Sprint Backlog. Daily Scrum. Test Cases. Results. Sprint Review Meeting. Release Burn chart.

PRODUCT BACKLOG The Product Backlog is the master list of all

functionality desired in the product. When using Scrum, it is not necessary to start a project with a lengthy, upfront effort to document all requirements.

SPRINT PLANNING MEETING The Sprint Planning Meeting is attended by the

Product Owner, the entire Scrum Team. During the sprint planning meeting the Product

Owner describes the highest priority features to the team.

The Product Owner doesn't have to describe every item being tracked on the Product Backlog.

SPRINT BACKLOG OF FIRST ITERATION

LAYOUT OF WEBSITE

DAILY SCRUM Meeting Between Product owner and developer Time: • 20-minutes

Three questions:• What did you do yesterday?• What will you do today?• What obstacles are in your way?

MENUS ON LAYOUT

LINKS ON MENUS LAYOUT

DISPLAY PRODUCTS ON MAIN PAGE

CUSTOMER ACCOUNT FORM

TEST CASE ITERATION ONE

RESULTS OF FIRST TWO WEEKS ITERATION

SPRINT REVIEW MEETING

Team presents what it accomplished during the sprint

Typically takes the form of a demo of new features or underlying architecture

Informal 2-hour prep time rule

Participants Customers Management Product Owner Other engineers

SPRINT BACKLOG OF SECOND ITERATION

CART IMPLEMENT

CUSTOMER ACCOUNT FORM

CUSTOMER FILLED THE FORM

CUSTOMER LOGIN

TEST CASE 2

RESULTS OF ITERATION TWO

THIRD ITERATION

ORDER PLACEMENT

AFTER ORDER PLACEMENT

FINAL RECEIPT IN PDF

TEST CASE 3

RESULTS OF ITERATION THREE

FOUR ITERATION OF SPRINT BACKLOG

ADMIN LOGIN FORM

ADMIN PANEL WITH MENUS

PAYMENT PANEL

TEST CASE 4

RESULTS OF FOUR ITERATION

CUSTOMER SATISFACTION GRAPH

RELEASE BURNDOWN On a Scrum project, the team tracks its progress against

a release plan by updating a release burn down chart at the end of each sprint. The horizontal axis of the release burn down chart shows the sprints months; the vertical axis shows the amount of work complete.

TOOLS AND LANGUAGES Presta shop (tool) Php6.0(Language) Mysql5.0 Apache 2.3 SqlYog Css HTML5.0 JavaScript

CONCLUSION Sprint to Sprint improve the progress of web

project Customer involve at the end of every sprint Requirements can recharge easily. Customer can change his/her mind at the end of

sprint Planning is proper sprint to sprint and get idea for

next iteration. Short term sprint is better than long term

duration. Changing requirements is very easy at the end of

sprint. Removes bugs sprint to sprint

REFERENCES [1] A Case Study on Agile Estimating and Planning using Scrum V. Manic (research paper) 2011. [2] A case Study on Impact of Scrum on Overtime and Customer

Satisfaction Engineering. 6/e, WCB McGraw Hill, New York, (white paper)2010. [3] Schatz B., Abdul shafi I. Primavera Gets Agile: A Successful Transition to Agile Development (white paper)2011. [4] Gerber, Aurona; Van der Merwe, Alta; Alberts, Ronell, Implications of Rapid Development Methodologies, CSITEd , Mauritius (research paper)2011. [5] Yatco, Mei Agile Joint Application/development. University of Missouri-St. Louis (research paper)2011. [6] Schell Jesse "Chapter Seven: The Game Improves Through scrum Iteration". The Art of Game .Design. Elsevier. pp. 79–95. ISBN 978-0-12- 369496-6 2010. [7] Carver J. Shull F. A checklist for integrating student empirical studies

with research and teaching goals // Empirical Software Engineering, (research paper)

2010.