Agile software delivery
Upcoming SlideShare
Loading in...5
×
 

Agile software delivery

on

  • 231 views

This presentation discusses the delivery of software using an agile approach. We open with the Agile Manifesto followed by a discussion of the mechanics of Scrum. We then discuss an agile team, how ...

This presentation discusses the delivery of software using an agile approach. We open with the Agile Manifesto followed by a discussion of the mechanics of Scrum. We then discuss an agile team, how the backlog fits into the picture, risk and how we can predict dates. This was presented to the Emerging Technology Class at Temple University on April 3rd, 2013.

Statistics

Views

Total Views
231
Views on SlideShare
231
Embed Views
0

Actions

Likes
0
Downloads
4
Comments
0

0 Embeds 0

No embeds

Accessibility

Categories

Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment
  • People are more important that tools and complex process. Working software is critical all of the time. Need to be flexible. But ….We still need tools, documentation and planning.
  • The Product is what we are building. Each of the features reside in the Product Backlog. The Product Owner know the most about the product and can prioritize the features in the backlog so the team is always working in the most important thing.The team knows what to do and are the experts. Management empowers them to be successful through trust and servant leadership.Release Planning meetings review the features in the backlog. These meetings prune, adjust and manage the backlog so the most important features are at the top of the list.The team delivers software in sprints of two to four weeks in duration. In the Sprint Planning meeting, the team adds features from the backlog into the sprint and agrees to complete them based on the definition of done. Ideally the DoD is potentially shippable.The team performs the work in the sprint in the manner they deem most appropriate. The team agreed to what can be completed so they have the power to decide how to work.At the end of each sprint the features are reviewed to validate that they meet the DoD. Anything that doesn't goes back into the backlog. The team has a discussion about what went well and what needs improvement. They agree to implement the improvements they have identified.Progress and status is transparent throughout the project and available to all.
  • Individuals and InteractionsCustomer CollaborationDeliver Software FrequentlyBusiness People and Developers work together DailyMotivated IndividualsFace to face conversation
  • Working SoftwareContinuous delivery of softwareWorking software primary measure
  • Individuals and InteractionsWorking SoftwareCustomer CollaborationResponding to ChangeValuable SoftwareWelcome Changing Requirements But … There are consequencesAttention to Technical ExcellenceSimplicity – the are of work not done…Self reflection
  • Individuals and InteractionsWorking SoftwareCustomer CollaborationResponding to ChangeValuable SoftwareWelcome Changing Requirements But … There are consequencesAttention to Technical ExcellenceSimplicity – the are of work not done…Self reflection
  • Customer collaborationResponding to changeAttestation to technical excellence
  • Mention the Iron Triangle
  • Responding to ChangeEarly and continuous delivery of softwareWelcome changing requirementsDeliver software frequentlyMotivated and trusted individualsWorking softwareAttention to technical excellenceSimplicity – the art of maximizing the amount of work not done

Agile software delivery Agile software delivery Presentation Transcript

  • • • • • • • • • • • • •2 Agile Software Delivery
  • 3 Agile Software Delivery
  • • • • •4 Agile Software Delivery
  • • • • • • •5 Agile Software Delivery
  • ••••••6 Agile Software Delivery
  • 7 Agile Software Delivery
  • 8 Agile Software Delivery
  • 9 Agile Software Delivery
  • 10 Agile Software Delivery
  • 11 Agile Software Delivery
  • • • • • • •12 Agile Software Delivery
  • 13 Agile Software Delivery
  • • • • • •14 Agile Software Delivery
  • 15 Agile Software Delivery
  • 16 Agile Software Delivery
  • 17 Agile Software Delivery
  • 18 Agile Software Delivery
  • 19 Agile Software Delivery
  • 20 Agile Software Delivery
  • • • • •21 Agile Software Delivery
  • • • •22 Agile Software Delivery
  • • • • • – – –23 Agile Software Delivery
  • 24 Agile Software Delivery
  • 25 Agile Software Delivery
  • 26 Agile Software Delivery
  • 27 Agile Software Delivery
  • 28 Agile Software Delivery
  • 29 Agile Software Delivery
  • 30 Agile Software Delivery
  • 31 Agile Software Delivery
  • 32 Agile Software Delivery
  • 33 Agile Software Delivery
  • 34 Agile Software Delivery
  • 35 Agile Software Delivery
  • 36 Agile Software Delivery
  • 37 Agile Software Delivery
  • 38 Agile Software Delivery
  • 39 Agile Software Delivery
  • 40 Agile Software Delivery
  • 41 Agile Software Delivery
  • 42 Agile Software Delivery
  • 43 Agile Software Delivery
  • 44 Agile Software Delivery
  • 45 Agile Software Delivery
  • • • • •46 Agile Software Delivery
  • • • • • • • •47 Agile Software Delivery
  • • • • • • • •48 Agile Software Delivery
  • 49 Agile Software Delivery