Agile methods
Sep. 24, 2011•0 likes•5,742 views
Download to read offline
Report
Technology
Business
A brief introduction to agile software development
DUONG Trong TanFollow
Recommended
Case Study on agile scrum methodology on shopping cartAbdullah Raza
Tech talks #1- Unit testing and TDDDUONG Trong Tan
Agile DevelopmentDennis Degryse
Scrum and Agile SDLC 101Aniruddha Ray (Ani)
Introduction to Project Management with ScrumPierre E. NEIS
Presentation on Agile Testing1Solutions Pvt. Ltd.
More Related Content
What's hot
What is agile modelSoftware Testing Books
AGILE METHODOLOGYDeepak Agrawal
What Is Agile ScrumMichael Bourque
10 differences between SAFe and LeSSStanislaw Matczak
Testing in agile projects – case studyArmands Baranovskis
Research paper presentation on agile scrumAbdullah Raza
Viewers also liked
Agile Software Development OverviewStewart Rogers
Implementing CQRS and Event Sourcing with RavenDBOren Eini
Keynote agile-in-vietnamAgile Vietnam
Introducing scrum into your organization ibelisDUONG Trong Tan
Agile estimation & planningDUONG Trong Tan
Release planning in ScrumArne Åhlander
Similar to Agile methods
Agile Software Development OverviewDUONG Trong Tan
SE18_Lec 05_Agile Software DevelopmentAmr E. Mohamed
Agile Project ManagementCici Conger-Portie, PgMP, PMP, PMI-ACP, MBA
SE_Lec 04_Agile Software DevelopmentAmr E. Mohamed
Agile Development with Scrum.pptxzuma14
Agile intro resourcesAnwar Sadat
More from DUONG Trong Tan
Trở thành Agile CoachDUONG Trong Tan
Coder nên biết thêm gì ngoài việc lập trìnhDUONG Trong Tan
Luyện cách hỏi DUONG Trong Tan
Building a Learning OrganizationDUONG Trong Tan
Giáo dục thông minh (Smart Education)DUONG Trong Tan
A reflection on constructivism and engineering educationDUONG Trong Tan
Recently uploaded
How resolve Gem dependencies in your code?Hiroshi SHIBATA
Chandrayaan 3.pptxPrasunJha12
GIT AND GITHUB (1).pptxGDSCCVRGUPoweredbyGo
"The Intersection of architecture and implementation", Mark RichardsFwdays
Meetup_adessoCamunda_2023-09-13_Part1&2_en.pdfMariaAlcantara50
9C Monthly Newsletter - SEPT 2023PublishingTeam
Agile methods
- 22. Managers maintain the right to authorize decision
- 23. Managers limit the information or resources available to workers
- 24. People decide what, and how to do
- 36. What will you do?
- 71. Smaller development items are often too small to be valuable and difficult to identify
- 72. Quality of requirements suffers as analysts rush to prepare for upcoming cycles
- 73. Quality of current development suffers when busy analysts are unable to inspect software or answer questions during development
Editor's Notes
- film
- A research and reflection of SomeBody:We are living in chaos: eco crisis, tech boom, changes …
- How to create a software from scratch?
- Parties:UsersHas problems to be solvedUsually disorganized, chaotic, groupCustomersProvides requirements and validationShould speak with “one voice”Developers Actually builds the stuff Lots of different roles hereBusiness Owner Manages resources and money Often ignored in Development Process…Tech concernsRequirementsDetermine What the Software has to do…Challenge: Satisfy the UsersProduction Actually Build the Software Challenge: Deliver Quality ProductMaintenance Modify Software to satisfy new requirements Challenge: Maintain Quality
- For reference and printing if needed, not for presenting
- Boehm, B.; R. Turner (2004). Balancing Agility and Discipline: A Guide for the Perplexed. Boston, MA: Addison-Wesley. pp. 55–57. ISBN 0-321-18612-5.
- Inherit from RAD
- Film firstVẽrađồhình Scrum3 PhútBạnnàocóthểgiúptôicắtnghĩatừ framework nhỉ? “độtnhiêntôithấybítừ”Kháiniệmkhunglàmviệc (framework) làgì?Tạisaokhônggọi Scrum làquytrình?
- Cross the mountainTraditional managers => ScrumMaster
- cross-functional = there is no strict role for individualsCode are collectively developed
- The importance of planning, not plan documentThe importance of responsibility -> select itemsThe importance of prioritizing -> reduce risksMake things clear
- Image , point to position
- Sutherland
- Architectural spike():very simple program to explore potential solutions, Most spikes are not good enough to keepMetaphor(an du): common vision of how the program works
- Courage(kien quyet)
- Introduced in XP
- SCM: svn,cvs, gitAutomated Build:Ant, Maven, MSBuild or IBM Rational Build ForgeAutomated tools: CruiseControl, Jenkins, Hudson
- Introduced in XP
- What does it mean?