Agile/Scrum Methodology Gains Your Productivity
•Download as PPTX, PDF•
1 like•926 views
"We are uncovering better ways of developing software by doing it and helping others do it. Through this work we have come to value: Individuals and interactions over processes and tools Working software over comprehensive documentation Customer collaboration over contract negotiation Responding to change over following a plan That is, while there is value in the items on the right, we value the items on the left more." This is the manifesto for Agile Software Development. Well, In this slide I tried to explain what actually agile is, what it's motive and the benefit at a glance. I rather used to explain by some meaningful picture then description. I also showed here the side by side methodology called Scrum, which is actually current trend at most of our software industries. Well, I guarantee it will not waste your time. Thank you.
More Related Content
What's hot
What's hot (20)
Viewers also liked
Viewers also liked (20)
Similar to Agile/Scrum Methodology Gains Your Productivity
Similar to Agile/Scrum Methodology Gains Your Productivity (20)
Recently uploaded
Recently uploaded (20)
Agile/Scrum Methodology Gains Your Productivity
- 1. None but, an acceleration on productivity Md. Hasan Basri Software Consultant
- 2. The Agile movement proposes alternatives to traditional project management. Agile approaches are typically used in software development to help businesses respond to unpredictability.
- 4. Team Based Incremental Iterative Value Driven Frequent Delivery Production Quality Inspect & Adapt
- 5. Does it provide steps? So, It guided some steps, Right?
- 6. So, How it differ from traditional waterfall?
- 8. Scrum is an agile software development model based on multiple small teams working in an intensive and interdependent manner. The term is named for the scrum formation in rugby, which is used to restart the game after an event that causes play to stop, such as an infringement.
- 12. 7 +/- 2 Cross functional Full time Self organizing Empowered Trust
- 14. Story points Story points vs. mandays Estimation meetings Planning poker Reference stories
- 19. Estimating using story points The most common way of estimating the size of user stories in Scrum is by allocating story points. Story points are just numbers drawn from a pool of numbers of a set size e.g. a story could have 1, 2, 3, 5, 8, 13, 20, 40 or 100 story points.
- 20. Poker Planning for Estimation
- 21. Size DurationCalculation 250 mh 250/25 = 10 days Velocity = 25 mh/day
- 29. What went well this sprint? What could we improve next sprint? Dev Environment, working practices, communication
- 30. Requires one day or less of work. Remaining effort is re-estimated daily, typically in hours. During Sprint Execution, a point person may volunteer to be primarily responsible for a task. Owned by the entire team; collaboration is expected.
- 31. Indicates total remaining team task hours within one Sprint Re-estimated daily, thus may go up before going down Intended to facilitate team self-organization Fancy variations, such as itemizing by point person or adding trend lines, tend to reduce effectiveness at encouraging collaboration Seemed like a good idea in the early days of Scrum, but in practice has often been misused as a management report, inviting intervention. The ScrumMaster should discontinue use of this chart if it becomes an impediment to team self-organization.
- 32. Tracks the remaining Product Backlog effort from one Sprint to the next. May use relative units such as Story Points for Y axis. Depicts historical trends to adjust forecasts.
- 33. Factors in scaling: Type of application Team size Team dispersion Project duration Scrum has been used on multiple 500+ person projects.
- 34. Individuals who commit to work together to reach a common goal.
- 35. Hard to plan No commitment Bad communication Competition and blaming Less value delivered
- 38. en.wikipedia.org/wiki/Agile_software_development http://cvcedhlab.hypotheses.org/54 scrummethodology.com www.mountaingoatsoftware.com › Agile www.allaboutagile.com/how-to-implement-scrum-in-10-easy-steps/ http://www.slideshare.net/jaaronfarr/scrum-agile-for-everyone?related=4 http://www.slideshare.net/hareshkarkar/overview-of-agile- methodology?related=5 http://www.slideshare.net/infolock/agile-presentation-6607073?related=6 www.scrumguides.org/docs/scrumguide/v1/scrum-guide-us.pdf http://mplaza.pm/downloads/Scrum Training Manual.pdf http://www.tutorialspoint.com/software_engineering/software_engineering_ pdf_version.htm Please excuse me if I missed some body’s reference unintentionally.