Agile Software Development Workshop at Sote Hub
0 likes228 views
The document discusses the limitations of the waterfall methodology in software development, particularly in startup environments where rapid changes and speed are crucial. It introduces agile development as a more flexible and iterative approach, highlighting its benefits such as adaptability, faster progress, and improved communication with customers. The document also describes key components of agile methodologies, including Scrum meetings and the importance of planning and retrospectives to ensure team efficiency and continuous improvement.
![References
[1] Agile Manifesto - http://agilemanifesto.org/principles.html
[2] Scrum Reference Card - https://www.collab.net/sites/default/files/uploads/
CollabNet_scrumreferencecard.pdf
[3] An Empirical Framework For Learning - http://scrummethodology.com](https://image.slidesharecdn.com/scrumeditedv2-170505174428/85/Agile-Software-Development-Workshop-at-Sote-Hub-21-320.jpg)
Agile Software Development Workshop at Sote Hub
- 1. Adapt to change and stay on track Agile Software Development
- 2. In the past: Waterfall
- 3. Waterfall (1) • Simple and very structured • Tasks may be assigned to specialised teams • Emphasis on documentation • Still useful • Large project • Requirements are clear • No, or very little change during development
- 4. Waterfall (2) - disadvantages • Can not see final product before very end • Blocking state • waste of resources during waiting for team • Inflexible - does not listen to changes during project.
- 5. How would you describe your product development experience in startup, could waterfall work? Question
- 6. Waterfall & startup world • Startups: • Typically Small projects • Very few requirements at the beginning • Uncertainty cause many changes happening very quickly • Speed of delivery is more important then perfection • Waterfall does not work in startup world
- 7. The need for speed • Industry needs to respond to unpredictable environment quickly
- 8. Question Do we need any developing methodology at all?
- 9. Yes, we need to be organised • Investors needs assurance of their investment and agile development helps. • Planning is critical • Measuring development progress • Stay on track
- 10. Agile (1) - Movement • Started to address the problems of Waterfall methodology • Agile tries to deliver software through incremental and iterative work • Changes based on an observation
- 11. Agile (2) - Benefits • Adaptable to changes • Fast progress and working software • Good communication with customer • Using TDD - What is TDD?
- 12. Scrum • Iterative and incremental agile software development framework for managing product development. • Application of agile development • Typically for 5 - 7 people, but possible to apply for smaller teams as well.
- 13. Agile (3) - Iterations
- 14. Scrum meetings • Planning - what? • Standup - daily scrum, update • Demo - sprint review • Sprint retrospective
- 15. Agile - Iteration terms • Backlog • List of all tasks which represent the product at time • Tasks are pulled from the backlog to the sprint • Sprint • One iteration • Typically one working week • At the end of the sprint, there should be working software possible to demo to stakeholders • Epic • Can be the goal of one or two sprints • Split the epic into two if it should take more then 3 sprints • Task • Typically more then one task is developed per person during the sprint • If is not, there is discussion what was the problem. The task can be split into two
- 16. Planning • Discuss first few tickets with highest priority in the backlog • Look on the backlog and estimate what work can be achieved within a sprint • Selected tickets is the aim of the work you are trying to achieve • Every team member must understand the tickets in the sprint
- 18. Standup • Team update • Catch up about previous day, or days • Depends on the team size, can be each day, once or twice a week • Its purpose is to synchronise team members and remove blockers - face the challenges
- 19. Demo - Sprint review • Demonstrate to your stakeholders finished tasks • If you are very small team with no stakeholders, you can show the work to your friends or team members from other companies • Its a good way to get a quick feedback
- 20. Retrospective • Team is talking openly about the week • Start • What should we start doing to work better as a team and be more efficient? • Stop • Is there something we should stop doing? • Continue • What are the good things we were doing and we should continue them?
- 21. References [1] Agile Manifesto - http://agilemanifesto.org/principles.html [2] Scrum Reference Card - https://www.collab.net/sites/default/files/uploads/ CollabNet_scrumreferencecard.pdf [3] An Empirical Framework For Learning - http://scrummethodology.com