Tuesday, March 29, 2016

Agile Software Development : Scrum


Scrum is a iterative and incremental agile software development framework for managing  development. An Iterative Project Management process. Does not include any engineering practices like XP.
Commonly used for product development 
Split into 3 Areas:
 -Roles  (Product owners, Scrum Master, Scrum Team)
- Ceremonies (Sprint Planning ,Sprint Review, Sprint Retrospective,)
- Artifacts (Sprint Backlog, Product Back log , Burn down chart)
 
Product Owner:
 - Maintain product backlog.
 - Define no of sprint .
 - Know domain knowledge.
 - Should understand business ,market , end user
 
Scrum Master:
- Enforce values and Practices.
- Removes impediments to progress.

 
Planning Meeting:
 - High Level overview of User stories.
 - Attended by all team members.
 - Stakeholders and users may attend.

Sprint Review:
- Shippable product at end of sprint
- Sprint assessed against goals
- Review is held with all team.
- Achieving goal is most important.
 
Sprint Retrospective:
- Attend by all including Product owner.
- 3 Questions:
    - What should be stop doing ?
    - What should be start doing.?
    - What should continue doing.?
Scrum VS XP
- Scrum duration is 2-4 weeks long called sprint
- XP duration is 1-2 weeks long.
- Scrum does not allow changes in sprint where as XP allows changes .
- Scrum product owner prioritizes the product backlog but the team determines the sequence in which they will develop the backlog item.
- Extreme programming team work in strict priority order.
-Scrum does not prescribe any engineering practices. where as extreme programing follow engineering practices like TDD, Pair programming and Continuous integration.

 
                                               Agile Team Practice Fundamentals
Principles:
- Iterative Delivery
- Frequent Feedback
- Transparency  and Openness
- Lean Principles
Extreme Programming(XP)
 Good Practice          Pushed to the  Extreme
 Code Reviews          Pair Programming
  Testing                     TDD and Constant regression
  Software  Design   Relentless Refactoring
  Simplicity                 The Simplest thing could possibly work
  Integration Testing   Continuous Integration
  Short Iterations       The Planning Game
                                            Agile Requirement and Estimation:
A requirement is
     - Independent
     - Negotiable
     - Valuable
      - Estimable
    - Size Appropriately
    - Testable
User Stories
As a <Role> I Want  <features> so that <benefit>.
Given <Context> when <something happens> then <desired result>
Example:

User Story: Customer’s Cash Withdrawal

As a Customer,
I want to withdraw cash from an ATM,
So that I don't have to wait in line at the Bank
 
                                                                   Estimation
Based on Size and complexity ,not duration
Story Points Value: Story points are unit of measure for expressing the overall  size of a user story , feature or task.
Use Planning Poker
    - XS,S,M,L,XL,XXL
    - 1,2,3,5,8,13,20,,40
    - 1,2,4,8,16,32
 
Sprint Velocity:Velocity is the number of story points completed by a team in an iteration.
 
We need velocity to: Predict how much scope can be delivered by a specific date Predict a date for a fixed amount of scope to be delivered Understand our limits while defining the amount of scope we will commit for a sprint -
How do we calculate velocity? Simple! We do some basic math.

Scenario: Our team delivers 3 user stories. The sum of the story points equals 20. Our velocity is then 20.

If, in the next iteration, our team delivers 30 story points, then our average velocity is 25, or (20 SP + 30 SP) divided by 2 iterations = 25 SP.
 
 
                                                  Burn - Down Chart
The sprint tracking is usually done using Burn-Down Chart. Burn-Down Chart shows the remaining effort in day-wise number of hours. For example, let us consider a 2-week sprint -
Sprint Duration: 2 Weeks
No. of Days per Week: 5
No. of Hrs. per Day: 6
No. of Resources: 6
Hence, total remaining effort at the beginning of sprint is 2*5*6*6 = 360 hrs.

Burn-up Chart

Burn-up chart’s mechanics is basically the same. The only difference is that instead of tracking how much work is left to be done, we track how much work we’ve completed, so the curve is going up, not down.

Agile Advantages:
  -Customer Satisfaction by rapid, continuous delivery of useful software.
  -People and interactions are emphasizing rather than process and tools.
 - Continuous attention and technical excellence and good design using TDD ,refactoring.
  - Regular adaption to changing circumstances.
  - Early return on investment.
  - Feed back from Real customers.
   - Build right product. 


Note: Creating Scrum Board using JIRA tool , follow below link for more info...
https://confluence.atlassian.com/agile/jira-agile-user-s-guide/creating-a-board
 

 

No comments:

Post a Comment