Solving Agile Project Management Challenges with TeamPulse
•
2 gefällt mir•1,497 views
This document provides an overview and agenda for a webinar on agile development with Telerik TeamPulse. The agenda covers Scrum planning in Sprint 0, an introduction to agile and Scrum in Sprint 1, the Scrum process in Sprint 2, Scrum metrics in Sprint 3, and a summary and Q&A in Sprints 4 and 5. The webinar discusses setting up a project in TeamPulse, capturing requirements, sprint and release planning, daily stand-ups, time tracking, testing, and reviews.
Empfohlen
Weitere ähnliche Inhalte
Was ist angesagt?
Was ist angesagt? (20)
Ähnlich wie Solving Agile Project Management Challenges with TeamPulse
Ähnlich wie Solving Agile Project Management Challenges with TeamPulse (20)
Mehr von Abhishek Kant
Mehr von Abhishek Kant (20)
Kürzlich hochgeladen
Kürzlich hochgeladen (20)
Solving Agile Project Management Challenges with TeamPulse
- 1. Telerik Agile Development with Telerik TeamPulse facebook.com/telerik.teampulse @team_pulse
- 2. Telerik Introductions Abhishek Kant • MCAD • Certified Scrum Master • Telerik India (+91-124-4300987) • abhishek.kant@telerik.com • @abhishekkant
- 3. 1 Webinar Day (WD) = 5 mins 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)
- 4. Telerik Sprint 0: Project Setup in TeamPulse
- 5. 1 Webinar Day (WD) = 5 mins 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)
- 6. The Current Process: Waterfall
- 8. The Future: Agile w/ Scrum
- 9. What is Scrum • ...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
- 10. What is Scrum II • ...uses self-organized teams, which define the best way to produce the highest priority functionalities • …is value-driven, not plan-driven • ...is focused on the prioritization of the work based on the highest business value for the customer.
- 11. 1 Webinar Day (WD) = 5 mins 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)
- 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 Continuous Communication– Activity Stream • Shows • Comments on Items • Discussions (like Twitter) • News from TeamPulse • Customizable Updates • User Configurable
- 14. Telerik Requirements Management via Backlogs Define Requirements • Capture work items • Refine requirements • Create tasks • Define Acceptance Criteria
- 15. Product Backlog => Sprint Backlog
- 16. Telerik Sprint & Release Planning Plan Work • Drag and drop prioritization • Plan Iterations • Schedule Iterations • Decompose work
- 17. The Sprint
- 18. What I did Daily Scrum Meeting What I will do What were the impediments
- 19. Telerik Daily Scrum Activity: Managing Work Managing and Tracking • My Perspective • My Task Board • Cross Project My Perspective
- 20. Telerik Daily Scrum Activity: Time Tracking Entering Time Your Way • By Tasks • By Timesheet Time Entries • Reviewing • Exporting
- 21. Telerik Agile Test Management • Acceptance Criteria • Traceability • Bug Management
- 22. Sprint Review
- 23. Finish by Sprint Retrospective
- 24. Retrospective in TeamPulse • Captured in Risks & Issues Section • Assigned to specific sprint • Can be commented on by individuals
- 25. 1 Webinar Day (WD) = 5 mins 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)
- 26. Team Velocity Scrum Metrics Sprint Burndown
- 27. Telerik Tracking Progress Track Progress • Project real time burn down • TeamPulse xView™ Cross Project Reporting Engine • Story Boards • Task Boards • TimeSheets
- 28. 1 Webinar Day (WD) = 5 mins 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)
- 29. Product Backlog User Stories Estimating Acceptance Criteria Scrum Artifacts Issues Bugs Sprint Backlog Product Increment
- 30. Sprint Planning Daily Scrum Scrum Ceremonies Sprint Review Sprint Retrospective
- 31. Telerik Sprint 5: Q&A facebook.com/telerik.teampulse @team_pulse
Hinweis der Redaktion
- 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