Agile: Scrum Presentation

Click here to load reader

Embed Size (px)

description

A short presentation about Agile: Scrum. How simple can you understand Agile: Scrum?

Transcript of Agile: Scrum Presentation

  • 1. Going back with the Philosophy and the Practice A day with ME: JOHN BATERNA

2. Manifesto for Agile Software Development Individuals and interactions Working software Customer collaboration Responding to change Processes and tools Comprehensive documentation Contract negotiation Following a plan That is, while there is value in the items on the right, we value the items on the left more. 3. The Product Backlog 4. Specific User/Persona/Role: John Baterna Acceptance Criteria - Reminder Remarks Desired feature Benefit from implementing the feature Secure log-in So that the access is registered and secured -List of login of each user -time stamp -IP registration -Lets use the same Network login [Usually being discussed with the development team] Reminder: Please make sure I can add the agencys contact persons; Full Name. Email, Mobile #, Office # w/local, Address include Country and Position Make sure it is a required field I can add one, two or more contact persons I can update their information anytime I can delete contact information Contact person can receive an email notification for any activity in the agencys profile; Edit or Update of the Agencys Profile and/or services -Signature here- 5. We assess and evaluate the Product Backlog, example Product Backlog below: 6. So we can come up with this; 7. So that we avoid this; 8. We monitor our progress by doing this: We burn all 9. Lets have a short activity in reading a user story 10. Reminder: Please make sure I can add the agencys contact persons; Full Name. Email, Mobile #, Office # w/local, Address include Country and Position Make sure it is a required field I can add one, two or more contact persons I can update their information anytime I can delete contact information Contact person can receive an email notification for any activity in the agencys profile; Edit or Update of the Agencys Profile and/or services -Signature here- The objectives are: Identify and clarify the acceptance criteria (Reminder) Which is/are the In-scope and out-scope items Plot the acceptance criteria Identify the task that is needed to accomplish the User Story Plot the identified task and do time (hours) assessment using Fibonacci (1,2,3,5,8,13,21) 11. We dont do much of this; 12. Because of many things like this; 13. Royce did not use the term "waterfall". Royce presented this model as an example of a flawed, non-working model. This, in fact, is how the term is generally used in writing about software developmentto describe a critical view of a commonly used software development practice. 14. The Business Side The Technical Side 15. Technology People Process User CustomerInfrastructure Business Business Circle This is my own interpretation - BATERNA 16. So what is exactly Agile as a methodology? What the heck am I talking about? It is a methodology with a variety of approach in a Humane way for doing work in a software development In software development it never was actually a scientific, manufacturing and engineering approach but a Social approach of being collaborative and treating software development as a new product development. Agile Methodology was created by a group of people (Developers, QA, Project Managers, Analyst, Designers and Marketing) for the same group of people to benefit with. 17. What will make us Technical Expertise Collaboration Self Management Honesty Open mindedness Humility Simplicity Transparency Self Trained Cross Functional Timeliness Initiative Proactive Humble 18. What will break us Neglecting End User Silo thinking Inflexibility Too much want with too less benefits No Recognition Hype Unrealistic Setting of Goal Being Impulsive Pain glory Being Impulsive! 19. Business Needs Is PriorityQuality 20. Scrum is a group of guys hugging each other supporting and pushing the opposition as try to capture and secure the ball beneath them, the ball must be rolled and passed behind the teams area to win the Scrum. 21. I.T in the business world 22. What is the best methodology? This is the wrong question life is more complicated than this. There is not one best methodology but a toolkit of methods to select. But if you choose your method you strictly do it right.