Not a member of Pastebin yet?
Sign Up,
it unlocks many cool features!
- Software development lifecycle
- Scrum е може би най-използваната agile методология за разработка на софтуер
- Work phases are generally separated to:
- - Idea
- - Planning
- - Creating
- - Testing
- - Deploying
- Горния процес обикновено е итеративен при гъвкавите методологии
- Environments – areas where product can be built, distributed, installed, configured and tested:
- - Development environment
- - Common build environment
- - Integration testing environment
- - User acceptance environment
- - Production environment
- В Development среда се разработва софтуера и след това се тества. Продукта пак бива изтестван в Staging среда и чак тогава ако тестването е успешно, продукта отива в Production средата
- ! Staging средата трябва да е със същите конфигурации като Production средата
- A development methodology is a set of practices and procedures for organizing the software development process
- - A set of rules that developers have to follow
- - A set of conventions the organization decides to follow
- - A systematical, engineering approach for organizing and managing software products
- Heavyweight and agile methodologies:
- - Heavy methodologies rely on formal procedures and documents
- - Agile methodologies rely on small iterations and less formalities
- Често полезни промени, като рефакториране, не се правят по продукта, защото тези промени не се счиатат за разумни, според manager-ите на проекта, например
- Agile methodologies:
- - Scrum
- - Kanban
- - Lean Software Development
- - eXtreme programming (XP)
- - и др.
- Scrum – an iterative and incremental agile software development methodology for managing product development
- Scrum roles:
- - Scrum master – maintains the Scrum process
- - Product owner – represents the stakeholders
- - Team – a group of about 7 people
- o The team does the actual development: analysis, design, implementation, testing, etc.
- Scrum terminology:
- - Sprint
- o An iteration in Scrum
- o Usually few weeks
- - Product Backlog – попринцип не е възможно да се измислят всички неща (функционалности), които ще трябва да се направят за конкретния продукт
- o All features that have to be developed
- - Sprint Backlog
- o All features planned for the current sprint
- Scrum practices:
- - Sprint planning meeting
- - Daily Scrum stand-up meeting – до 15 минути
- - Sprint review meeting
Add Comment
Please, Sign In to add comment