Collaborative Agile Development with TeamPulse
Upcoming SlideShare
Loading in...5
×
 

Like this? Share it with your network

Share

Collaborative Agile Development with TeamPulse

on

  • 1,040 views

 

Statistics

Views

Total Views
1,040
Views on SlideShare
917
Embed Views
123

Actions

Likes
0
Downloads
23
Comments
0

1 Embed 123

http://telerikhelper.net 123

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
  • 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.
  • Theteamdoesthedevelopmentworkoftheproductincrementthat hasbeenplanned,aimingtofulfill thestablishedSprintGoal
  • 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?
  • ThentheteammeetstheProduct Ownerandstakeholders forthe SPRINTREVIEWandpresentstothemwhatwasproducedduringtheSprint
  • Rightafterthat,theteamhelds the SPRINTRETROSPECTIVE,whereitdiscusses whatwentwell andwhatcould beimprovedforfutureSprints

Collaborative Agile Development with TeamPulse Presentation Transcript

  • 1. facebook.com/telerik.teampulse @team_pulseTelerikAgile Developmentwith Telerik TeamPulse
  • 2. TelerikIntroductionsAbhishek Kant• MCAD• Certified Scrum Master• Telerik India (+91-124-4300987)• abhishek.kant@telerik.com• @abhishekkant
  • 3. 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
  • 4. TelerikSprint 0: Project Setup in TeamPulse
  • 5. 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
  • 6. The Current Process: Waterfall
  • 7. The Future: Agile w/ Scrum
  • 8. • ...is a simple agile framework• ...uses the iterative and incremental approach to enhancevisibility and reduce risks• ...helps to deliver value frequently, in a shorter timeto the customer• ...use frequent inspection and adaptation tocontinuously improve the product and thedevelopment processesWhat is Scrum
  • 9. What is Scrum II• …is value-driven, not plan-driven• ...uses self-organized teams, which define the bestway to produce the highest priority functionalities• ...is focused on the prioritization of thework based on the highest businessvalue for the customer.
  • 10. 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
  • 11. The Scrum Team• Product Owner• Ensures and maximizes the ROI for the customer fromthe work of the Team• Team• Self-organizes. Generates value for thecustomer, building high quality product increments• ScrumMaster• Ensures that the values, practices and rules of Scrumare understood and followed
  • 12. Telerik• Shows• Comments on Items• Discussions (like Twitter)• News from TeamPulse• Customizable Updates• User ConfigurableContinuous Communication– Activity Stream
  • 13. TelerikDefine Requirements• Capture work items• Refine requirements• Create tasks• Define AcceptanceCriteriaRequirements Management via Backlogs
  • 14. Product Backlog => Sprint Backlog
  • 15. TelerikPlan Work• Drag and drop prioritization• Plan Iterations• Schedule Iterations• Decompose workSprint & Release Planning
  • 16. The Sprint
  • 17. What I didWhat I will doWhat were theimpedimentsDaily Scrum Meeting
  • 18. TelerikManaging and Tracking• My Perspective• My Task Board• Cross Project My PerspectiveDaily Scrum Activity: Managing Work
  • 19. TelerikEntering Time YourWay• By Tasks• By TimesheetTime Entries• Reviewing• ExportingDaily Scrum Activity: Time Tracking
  • 20. Telerik• Acceptance Criteria• Traceability• Bug ManagementAgile Test Management
  • 21. Sprint Review
  • 22. Finish by Sprint Retrospective
  • 23. Retrospective inTeamPulse• Captured in Risks & Issues Section• Assigned to specific sprint• Can be commented on by individuals
  • 24. 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
  • 25. Scrum Metrics Team Velocity Sprint Burndown
  • 26. TelerikTracking ProgressTrack Progress• Project real time burn down• TeamPulse xView™ CrossProject Reporting Engine• Story Boards• Task Boards• TimeSheets
  • 27. 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
  • 28. Scrum Artifacts Product Backlog User StoriesEstimatingAcceptanceCriteria Issues Bugs Sprint Backlog Product Increment
  • 29. Scrum Ceremonies Sprint Planning Daily Scrum Sprint Review SprintRetrospective
  • 30. facebook.com/telerik.teampulse @team_pulseTelerikSprint 5: Q&A