This document discusses an upcoming webinar on adopting Agile practices. It provides an overview of Agile concepts like iterative development, working software, and responding to change. It then discusses Scrum roles, ceremonies, and artifacts. The webinar aims to explain what's in it for stakeholders like customers, project managers, and team members in making the transition to Agile. Attendees are prompted to consider action items they can implement. Upcoming related trainings in Boston are also advertised.
Scrum feb 3rd - manoj vadakan - cosncires agile practices
1. Going Agile? What is in it for me? Hosted By Manoj Vadakkan Bachan Anand Conscires Agile Practices agile@conscires.com Manoj Vadakkan manoj@vadakkan.org
16. Homework Problem 11 http://alistair.cockburn.us/Are+iterations+hazardous+to+your+project%3F
17. The Homework ProblemIterative vs. Agile A School homework assignment Read 10 books answer 20 questions Submit answers by Following Monday (1 week to complete the assignment) 12 http://alistair.cockburn.us/Are+iterations+hazardous+to+your+project%3F http://www.scrumalliance.org/articles/134-iterative-vs-agile
20. Homework ProblemThe plan Read two book every day (M-F) Spend Saturday to answer questions Submit answers on Monday 15
21. Homework ProblemWhat Really Happened Student read books as per plan. Status on Friday - Green Started looking at questions on Saturday to realize that books need to be read again for the most part Status on Saturday - Red 16
22. What is the point? How the student should have measured his progress? Number of Books read? Number of Questions answered? How do you measure progress in your projects? 17
56. What Challenge do you have? What challenges do you have in your environment? 51
57. Why Agile? We may have better process efficiency than we ever had before. How do we improve now? Is the budget/schedule getting shorter? How about value delivered & Time to Market?
58. Business Value Is prioritization an afterthought? When/who prioritize features? Late? may be when we are really sure we can not do it all within the time?
60. Reasons for Project Failure 55 Extracted from CHAOS Report : The Standish Group 1995
61. 56 Reasons for Project Success Extracted from CHAOS Report : The Standish Group 1995
62. What is in it for me? As a customer , I want to be able to Go to market faster Faster return on investment Opportunity to provide feedback early As a Project Manager/Leadership, I want To measure progress in terms of real progress made on product . Better engaged and accountable team As a team member, I want A sustainable pace Satisfaction of quality product delivered Clear Priority and less interruption during development 57
64. Scrum A process framework for managing product development Not a methodology 59
65. Agile Product Development Product Owner with Stakeholders/PMO Multiple sprints usually build up a release Product Backlog Production Release Feedback from Sprint Reviews Discovery Period Feedback from Releases Sprint = Iteration Product Owner with Stakeholders/PMO During the Discovery Period, the product team identify the features, prioritize the features, and identify a roadmap for the product. The roadmap will identify the release milestones into production and the features contained in each releases at a high-level. Each Sprint deliver (for a subset of Product Backlog) running tested features potentially shippable that the team can demonstrate to the customer to get feedback
66. Agile Product Development: Sprints Initial Analysis for the sprint backlog The team creates working software for the features selected for the Sprint including all the necessary Documentation Acceptance Criteria Defined for Sprint Sprint Backlog Product Backlog Sprint Demo Potentially shippable product Sprint Task List Sprint Product Owner with Stakeholders/PMO Sprints are of the consistent, fixed length for a project, usually 1 week to 4 weeks. With the help of the Product Owner, the team selects a set of features from the top of the prioritized product backlog. Team Spends 2 to 4 hours on the first day of the sprint to break down the features to detail tasks (technical, testing, documentation, etc) and estimate hours needed to complete them. Within the sprint the team deliver Running Tested Features along with all the documentation for the selected features. The product from the sprint is demonstrated to the customer to get feedback.