Scrum for IT Offshore & IT Outsourcing in Asia

  • 3,443 views
Uploaded on

An agile development approach in Offshore Software Development

An agile development approach in Offshore Software Development

More in: Technology , Business
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
  • HI dear i am Priscilla by name, i read your profile and like to be in contact with you, that is why i drop this note for you, please i we like you to contact me in my privet mail box to enable me send my picture to you,and also tell you more about me thanks i we be waiting for your reply, (bernard_priscilla@yahoo.com)
    Are you sure you want to
    Your message goes here
No Downloads

Views

Total Views
3,443
On Slideshare
0
From Embeds
0
Number of Embeds
2

Actions

Shares
Downloads
0
Comments
1
Likes
5

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. Scrum @ IT Outsourcing Asia
    An agile development approach in IT Outsourcing
  • 2. SCRUM
  • 3. SCRUM
    • Scrum allows software to be developed in an environment where requirements can be defined and changed during the project.
    • 4. Scrum is a simple but powerful framework for development teams and customers to inspect and adapt as the product is produced.
    • 5. Scrum provides a high degree of clarity and transparency to all who are involved. – Team, Customer, Management and others.
    • 6. Scrum encourages finding and eliminating weak spots and allows teams and organizations to continuously improve their effectiveness
  • Product Owner
  • 7. Product Owner
    • The Product Owner owns the vision of what should be produced to achieve success.
    • 8. The Product Owner role is performed by the customer, supported by a Product Manager of IT Outsourcing Asia.
    • 9. The Product owner gets input from the customer organization and translates this into a single list of what should be produced.
    • 10. The Product owner prioritizes this list based on business value and risk.
    • 11. This list is called “Product Backlog”
  • Product Backlog
  • 12. Product Backlog
    • The Product Backlog is the single Master list of features, functionalities and other works that could be developed.
    • 13. The list is ordered by priority. Priority is determined by the Product owner based on business value and risk.
    • 14. Items at the top will be completed by the team sooner.
    • 15. The Product Backlog is constantly being revised (adding and removing items, re-ordering) by the product owner.
    • 16. The product is finished when the product owner decides it is. Not necessarily when the Product Backlog is empty.
  • The Team
  • 17. The Team
    • The Team consists of everyone who is working on the product, and is cross-functional. It has all the skills to produce a finished product – designers, developers, testers etc.
    • 18. Everyone contributes based on competency, rather than just job title.
    • 19. The team is self-organizing and self-managing. It is responsible
    for making a commitment and managing itself to hit the goal (or
    get as close as it can).
    • All Team members are responsible for the teams success.
  • Sprint
  • 20. Sprint
    • The Team works on the product for fixed periods of time, called sprints.
    • 21. Sprints are 2 or 4 weeks in time. Sprint length is determined by product owner and product manager in advance.
    • 22. Sprints occur one after another, without downtime in between.
  • Sprint Planning Meeting
  • 23. Sprint Planning Meeting
    • Before each sprint the team decides what it will commit to deliver by the end of the sprint, starting at the top of the product backlog.
    • 24. The Team creates a task-level plan how they will deliver.
    • 25. The Team works together to define an initial task assignment and compares total estimated task hours with total estimated hours to make sure the commitment is reasonable.
    • 26. Everyone of the team takes part.
    • 27. Once the Sprint planning is completed it will be presented to the Product Owner.
  • Sprint Planning Meeting
    • It Is very important that the Product owner does not pressure the team into committing more than they think is doable. If the team is pressured they will over commit and either not finish or burn themselves out after a couple of sprints.
    • 28. Many managers are initially concerned that the team might under commit. In reality teams are more likely to over commit.
  • No Changes
  • 29. No Changes
    • During a sprint the content and duration do not change.
    • 30. This enables the team to make and keep their commitments. It gives the team focus and stability during the sprint and it trains the product owner to clearly think through what is on the Product Backlog.
    • 31. If the goal of a sprint becomes obsolete the Product owner can direct the team to cancel the sprint and start a new one.
    • 32. In return for not making changes during a sprint the Product owner can makeany change to the Product backlog before the start of the next sprint.
  • Daily Scrum Meeting
  • 33. Daily Scrum Meeting
    • Each day the team has a short meeting to update each other on progress, risks and blocks.
    • 34. To keep the meeting below 15 minutes everyone answers just 3 questions:
    • 35. What work did you complete yesterday?
    • 36. What work are you planning to complete today?
    • 37. What problems and risks you are facing?
    • 38. The Scrum Master notes problems and risks and helps solve them after the meeting.
    • 39. After the meeting the progress report will be updated and made available to all interested parties.
  • Progress Report
    • Progress is reported in the following ways:
    • 40. Task backlog, which list the status of all the individual tasks.
    • 41. Burn Down Chart, which sets the work remaining against the time remaining.
  • Scrum Master
  • 42. Scrum Master
    • The Scrum Master serves the team by helping them to remove obstacles.
    • 43. He protects the team from any outside disturbance or interference
    • 44. He teachesand guides the use and implementation of Scrum within the team.
    • 45. Without a Scrum Master the team has a high risk of failure.
    • 46. The Scrum Master is part of the team and is not a project manager
  • Sprint Result
  • 47. Sprint Result
    • The aim of the team is to deliver 100% what they have committed to deliver.
    • 48. Ideally the end of a sprint results in an increment to a potentially shippable product.
    • 49. This means the functionality has been designed, implemented and fully tested, with no major defects.
    • 50. An individual task is either completed or not completed. Only completed tasks will be delivered.
  • Sprint Review
  • 51. Sprint Review
    • At the end of a Sprint the result of the sprint is presented to the Product Owner.
    • 52. Feedback and suggestions from the Team are also provided to the Product Owner.
    • 53. The Product owner can incorporate this feedback into the Product Backlog
    • 54. The Product owner can provide feedback to the Team.
    Feedback about the product will be incorporated into the Product Backlog. Feedback about the process can be send to the Product Manager.
  • 55. Sprint Retrospective
  • 56. Sprint Retrospective
    • At the end of each sprint the Team meets to reviews their way of working and looks for ways to improve their effectiveness.
    • 57. Any input / suggestions made by the Product Owner will also be discussed in this meeting.
    • 58. Minutes of this meeting will be made available to all interested parties.
    • 59. This is the mechanism for continuous improvement and also where issues are addressed and surfaced to the management or product owner for assistance.
  • Project Members
    Customer IT Outsourcing Asia
    Product Owner
    Product Manager
    Scrum Master
    The Team
  • 60. Project Members
    • For success of the Project active participation of all Project Members is required.
    • 61. All Team Members have access to all information about the Project.
    • 62. All Project Members are equal. There is no hierarchy and everyone is responsible for the success of the project.
    • 63. All Project Members can communicate directly.
    • 64. Communication can be done directly using Chat, voiceor e-mail.All written communication will be logged and made accessible to all Project members.