🗊Презентация Software Development Life Cycle and Methodologies

Software Development Life Cycle and Methodologies

Agenda Self-study, home work discussion. Questions. SDLC. Processes. What is Agile? Scrum, Waterfall, XP… Practice.

What is SDLC?

Processes. Why do we care about it?

For any company Customer satisfaction critical Project should end successfully all the time Project: complex NEW DIFFERENT software products Different size, different teams, different locations, distributed development

SDLC gone wrong

Software Development Methodologies Waterfall Iterative RUP Agile XP …

Traditional Approach

What is Agility?

Agile Manifesto Individuals and interactions over processes and tools Working software over comprehensive documentation Customer collaboration over contract negotiation Responding to change over following a plan

Roles Product owner – The Product Owner is a member of the Scrum team charged with maximizing the value of the team’s work. The product owner holds the product vision and works closely with stakeholders, such as end users, customers, and the business to cultivate and nurture a community around the product. Scrum Master – The Scrum Master is a servant leader, helping the rest of the Scrum team progress. He keeps the Scrum team productive and learning. He needs Coach the team, Keep the team moving forward and Help everyone understand Scrum. Team – The entire team (5-9 people), work together to achieve results. The development team does the actual work of delivering the product increment. The team is a cross-functional group of professionals who, among them, have all the necessary skills to deliver each increment of the product.

Meetings Sprint Planning – the team meets the Product Owner to choose a set of items to deliver during the next sprint. Daily Standup (Daily Scrum) – the team meets each day to synchronize and identify impediments. Sprint Review – the team reviews and demonstrates to the Product Owner what is has completed during the Sprint. Sprint Retrospective – the team looks for ways to improve the processes. Backlog Grooming – the team meets with Product Owner to estimate product Backlog, refine the acceptance criteria for individual stories, and break larger stories into smaller ones.

Artifacts Product increment – an integrated, shippable product (build) Product Backlog – a prioritized list of desired project outcomes or features Sprint Backlog – a set of work from the Product Backlog that the team agrees to complete in a Sprint, broken down into tasks Burn Down Chart – view of the work remaining Task Board – active sprint board with the tasks in statuses like “To Do”, “In Progress”, “Done”

Scrum Visualization

Result: Continuous improvements

Scrum vs Kanban

Waterfall Development

Iterative Waterfall development

Scrum Development

Lean Development

V-model

Scrum vs Waterfall in reality

Practice: Scrum Penny Game

Why Agile works? Less functional on iteration, less risks and wrong estimates. Fast rump-up (no need in deep review of docs) Often releases – REAL PROGRESS

Materials for self-study Book: Scrum and XP from the trenches (Link: http://wwwis.win.tue.nl/2R690/doc/ScrumAndXpFromTheTrenchesonline07-31.pdf) Article: http://all4agile.com/en/differences-between-waterfall-iterative-waterfall-scrum-and-lean-software-development-in-pictures/ Video: http://scrumtrainingseries.com/ (ALL) Scrum vs Kanban: https://youtu.be/rIaz-l1Kf8w Describe what methodology would you use to develop/test … example