An agile development approach in Offshore Software Development

1. Scrum @ IT Outsourcing Asia An agile development approach in IT Outsourcing

2. SCRUM

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.

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.

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.

18. Everyone contributes based on competency, rather than just job title.

21. Sprints are 2 or 4 weeks in time. Sprint length is determined by product owner and product manager in advance.

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.

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.

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.

40. Task backlog, which list the status of all the individual tasks.

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.

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.

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

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.

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.