9. • ...is a simple agile framework
• ...uses the iterative and incremental approach to enhance
visibility and reduce risks
• ...helps to deliver value frequently, in a shorter time
to the customer
• ...use frequent inspection and adaptation to
continuously improve the product and the
development processes
What is Scrum
10. What is Scrum II
• …is value-driven, not plan-driven
• ...uses self-organized teams, which define the best
way to produce the highest priority functionalities
• ...is focused on the prioritization of the
work based on the highest business
value for the customer.
11. Agenda
Sprint 0: Scrum Planning (2 WD)
Sprint 1: What is Agile & Scrum (2 WDs)
Sprint 2: The Scrum Process (4 WDs)
Sprint 3: Scrum Metrics (1 WD)
Sprint 4: Summary (1 WD)
Sprint 5: Questions (1 WD)
1Webinar Day (WD) = 5 mins
12. The Scrum Team
• Product Owner
• Ensures and maximizes the ROI for the customer from
the work of the Team
• Team
• Self-organizes. Generates value for the
customer, building high quality product increments
• ScrumMaster
• Ensures that the values, practices and rules of Scrum
are understood and followed
13. Telerik
• Shows
• Comments on Items
• Discussions (like Twitter)
• News from TeamPulse
• Customizable Updates
• User Configurable
Continuous Communication– Activity Stream
The development world has moved from waterfall to agile development process. In this session, we will start with understanding the Agile project management process. A good tool is important as you implement the Agile methodology for your distributed team. We will delve into implementing the Agile processes for your team using Telerik TeamPulse. See how TeamPulse caters to requirements gathering & planning to defect management. You will learn how to easily monitor progress of your projects and keep track of effort spent on it.
Ask for current challenges that project faces
Agile software development is a style of software development characterized by an emphasis on people, communication, working software, and responding to change.
The Scrum Framework in 30 SecondsA product owner creates a prioritized wish list called a product backlog.During sprint planning, the team pulls a small chunk from the top of that wishlist, a sprint backlog, and decides how to implement those pieces.The team has a certain amount of time, a sprint, to complete its work - usually two to four weeks - but meets each day to assess its progress (daily scrum).Along the way, the ScrumMaster keeps the team focused on its goal.At the end of the sprint, the work should be potentially shippable, as in ready to hand to a customer, put on a store shelf, or show to a stakeholder.The sprint ends with a sprint review and retrospective.As the next sprint begins, the team chooses another chunk of the product backlog and begins working again.
Meetings are targeted to complete in 10 to 15 minutes. Each member in turn answers three questions: What did I do since the last Scrum meeting? What do I plan on doing between now and the next Scrum meeting? Do I have any roadblocks?