Understand Agile and Scrum Methodology in Software Development

agile development and scrum methodology n.w
1 / 13
Embed
Share

Dive into the world of Agile and Scrum methodologies, exploring their benefits and drawbacks. Learn about the evolution from traditional waterfall development to agile practices, the core principles of Agile Manifesto, the roles in Scrum teams, sprint planning and execution, and the importance of breaking down tasks in the planning process.

  • Agile Development
  • Scrum Method
  • Software Development
  • Agile Manifesto
  • Sprint Planning

Uploaded on | 1 Views


Download Presentation

Please find below an Image/Link to download the presentation.

The content on the website is provided AS IS for your information and personal use only. It may not be sold, licensed, or shared on other websites without obtaining consent from the author. If you encounter any issues during the download, it is possible that the publisher has removed the file from their server.

You are allowed to download the files provided on this website for personal or commercial use, subject to the condition that they are used lawfully. All files are the property of their respective owners.

The content on the website is provided AS IS for your information and personal use only. It may not be sold, licensed, or shared on other websites without obtaining consent from the author.

E N D

Presentation Transcript


  1. Agile Development and Scrum Methodology

  2. Overview Discuss Agile and Scrum What it is Benefits Negatives Let s look at IAB data

  3. Agile software development Evolution of the waterfall: First get requirements Develop Then release Benefits: Actions happen in lockstep Steps can be completed before the next step Negatives: If the things on the ground change, you can t adapt. (e.g. mobile devices become important)

  4. Agile Tight iteration of design, build, test, release Adapt all the time Small teams, short duration http://agilemanifesto.org Benefits Continuous improvement Change quickly to change Constant feedback Negatives Constantly testing ideas Hard to scale Hard to conform to standards

  5. Scrum Method (one of several) to implement agile Team makeup Product manager - represents the customer/owner Scrum master - manages the scrum team Protects the team from distractions Organizes the scrum board Ensures everyone is working at optimal efficiency Scrum team - small team with expertise User Studies - executes the evaluation Everyone knows their jobs Everyone codes, everyone talks to users, everyone participates in evaluation

  6. Sprint A block of time 2 weeks to 1 month Don t change sprint goals You will do one week sprints Start of sprint - sprint plan Daily scrum meetings What did you work on yesterday? What are you working on now? Is anything blocking you? End of sprint Retrospective (Lead: SM) Test/Build/Release (Lead: SM) Show customer latest designs, build, etc. (Lead: PM, US)

  7. Plan Retro Standup Standup Standup Demo Plan Standup Retro Standup Standup Plan Retro Standup Demo Standup Standup Plan Retro Standup Standup Standup

  8. Planning Break up tasks into epics, stories, tasks, and subtasks Epics - large goals Address a user need Stories - As a X, I want to do Y to Z. Tasks - things that will need to be developed to realize stories Sub-tasks - breaking down tasks into smaller sized chunks Planning poker Points Let s go through an exercise: I want to address the issue of getting the best deal when shopping on the internet.

  9. Planning I want to address the issue of getting the best deal when shopping on the internet. Epics - large goals Address a user need Stories - As a X, I want to do Y to Z. Tasks

  10. Standup Daily scrum meetings What did you work on yesterday? What are you working on now? Is anything blocking you? Let s Roleplay

  11. Retrospective What worked well What didn t work well What did we want to work on this week Code review PM and US show latest draft to customers

  12. Minimal Viable Product When developing a solution to a task, consider it a hypothesis. Develop the minimal viable product to evaluate the hypothesis

  13. Agile/Scrum Breakdown goals for targets months away Identify realistic capacity Identify if you are on pace to achieve goals Plan for the interdisciplinary teams Negatives More overhead, but i think more efficient Better planning, less stress Good Agile management systems: Trello, Jira Agile for life https://www.youtube.com/watch?v=J6oMG7u9HGE

Related


More Related Content