Agile Software Development And Testing

1y ago
24 Views
2 Downloads
1.42 MB
46 Pages
Last View : 8d ago
Last Download : 5m ago
Upload by : Giovanna Wyche
Transcription

Agile Software Developmentand TestingIana MourzaQE/Release/Automation LeadVMware, Inc.2007-20121

Ground Rules for this classStart on time, end on time Electronics use – only by exception (isn’t itsurprising?) One conversation at a time No cell phones, please

Agile Software EngineeringDifferent names SCRUM XP (extreme programming) Lean development

Agile Software Engineering similar methodology: Incremental framework for software projectdevelopment Introduced to accommodate rapid productchanges Frequent releases in short development cycles(sprints, timeboxing etc) Minimal requirement, spec and testdocumentation (if at all) Often – no formal test cases

Agile Software Engineering

Agile Software EngineeringTraditional software development models: Pre-defined set of features, low requirements churnDelivering large pieces of software (incrementaldevelopment) or entire product (waterfall) at once longer development periods less stabilityAgile software development model: Dynamically defined/prioritized set(s) of featuresDelivering smaller pieces, one by one shorterdevelopment periods more stability

SCRUMWhat is Scrum?

SCRUMWhat is Scrum?

SCRUMWhat is Scrum?

SCRUMWhat is Scrum? Type of Agile software engineering Iterative and incremental framework forsoftware engineering Process with pre-defined set of practices androles

SCRUMWhy? To maximize team’s ability to deliver quickly andrespond to evolving and changing requirements. To develop functionality in smaller and stableincrements (as opposite to one large unstablebundle) – have potentially deliverable product inshorter periods of time

SCRUM – How?By short development cycles (Sprints):

SCRUM – TeamForm a Scrum team: Scrum Master (maintains the process) Product Owner (represents the stakeholdersand the business) Team (cross-functional group – Dev, QA,Architects, Business Analysts etc) Team size: 5-9, co-located If need to scale – add more Scrum teams

SCRUM – TeamScrum Master: Leads the teamFacilitates and coordinates everythingHelps removing the obstaclesSafeguards the processActs as “sheepdog” for the teamCan be anyone with necessary skills

SCRUM – TeamProduct Owner: Business-oriented, defines product backlogPrioritizes featuresOwns vision of the productOwns release dates/costsOpen to negotiations with the TeamCan be Product/Project/Marketing Manager

SCRUM – TeamTeam: Developers, QAs, Architects, Analysts, Tech Writers,Subject matter experts etc.Actually does the workResponsible for estimates and planning thework/risksDo all the needful to deliver on schedule

SCRUM – TeamBasic Team building principles: fective CommunicationsSelf-organized and self-led

SCRUM – ProcessSprint Basic unit of development in ScrumTimeboxed (restricted to a specific duration) effortof a constant lengthTeam decides the durationTypically - 1 to 4 weeksBefore Sprint: planning meetingAfter Sprint: review/demo and retrospective

SCRUM – ProcessProduct Backlog: Defined by Product Owner/TeamPrioritized by Product OwnerReviewed and re-prioritized before project startsand before each Sprint

SCRUM – ProcessSprint Backlog: Defined/Prioritized by Product Owner/TeamList of items to be done within next sprintEach feature is broken down into tasksEach task is 4-16 hrs of work

SCRUM – ProcessBurn Down chart: Tracks the progress in labor or work units – done, total,leftIn class, we use topics/slides covered7060504030201007:00 7.30 8:00 8:30 9:00 9.30 10:00 10:30 11:00PM PM PM PM PM PM PM PM PM

SCRUM – ProcessSprint Planning Meeting: Held at the beginning of the sprint (every 7-28 days)Select what work is to be donePrepare the Sprint Backlog that details the time it will take to dothat work, with the entire team Identify and communicate howmuch of the work is likely to be done during the current sprintEight hours limit (1st four hours) Product Owner Team: dialog for prioritizingthe Product Backlog (2nd four hours) Team only: hashing out a plan for the Sprint,resulting in the Sprint Backlog

SCRUM – ProcessSprint Review Meeting: Held at the end of each Sprint cycleReview the work that was completed and notcompletedPresent the completed work to the stakeholders (a.k.a.“the demo”)Incomplete work cannot be demonstratedFour hour time limit

SCRUM – ProcessSprint Retrospective: Held at the end of each Sprint cycleAll team members reflect on the past SprintMake continuous process improvementsTwo main questions are asked in the sprintretrospective: What went well during the sprint? What could be improved in the next sprint?Three hours limit

SCRUM – ProcessDaily Scrum/Standup: Held daily, same location and same time every dayThe meeting starts precisely on time.All are welcome, but normally only the core roles speakThe meeting is timeboxed to 15 minutesEach team member answers three questions: What have you done since yesterday? What are you planning to do today? Any impediments/stumbling blocks?Scrum Master facilitates resolution of impediments, although theresolution should occur outside the Daily Scrum itself to keep itunder 15 minutes.

SCRUM – ProcessDefinition of DONE (DoD): What “Done” means should be defined BEFORESprint startsIndividual for each Sprint teamAll Sprint team members should agreeCannot be changed once Sprint startsShould be concrete and measurableDefines deliverables for each Product Backlog item“Sashimi” – a report that something is DONE.

SCRUM – ProcessSprint results: If at the Sprint Review Meeting the acceptance criteriaof “Done” are not met – the item(s) is NOT DONE andSprint failed. There are no “Partially Done” Sprints.

SCRUM – ProcessAbnormally terminated Sprint: The Product Owner can cancel a Sprint if necessary withinput from the team, scrum master or management.Management may wish to cancel a sprint if externalcircumstances negate the value of the sprint goal.If a sprint is abnormally terminated, the next step is toconduct a new Sprint planning meeting, where thereason for the termination is reviewed.

SCRUM – ProcessInside the Sprint: The development/testing done by delivery teamDaily scrums held to report progress/impedimentsProduct owner monitors the progress and backlogprioritiesScrum Master facilitates everythingDays are busy!

SCRUM – ProcessSprint at a glance:

SCRUM - Exercise Run one Sprint for a project:Website “How to decorate a House for Mother’sday”Site is informational, we are not selling anything

SCRUM - Exercise 3-4 teams (5-9 people each) Within each team, define roles: Scrum Master (1) Product Owner (1) Team (3-7)

SCRUM – Exercise Select a page topic from Product backlog : Decoration materials (types, colors, where toget the supplies) Decorating with flowers Decorating with lights and toys Decorating with food Decorating with household items Last-minute decoration ideas “Green” decoration practices Safety measures

SCRUM – Exercise What to do in each team:Create a page (set of pages) on assigned topic Represent graphics and UI controls Can contain pictures/graphics (can you draw?) “Daily” Scrums! (every 15 mins) All pages should have consistent look and feel All pages should represent ONE site ( ScrumMasters/Product Owners should coordinate betweenthe teams on how pages are integrated and who isdoing the Main Page) DO NOT FORGET TO TEST!

SCRUM – Exercise Definition of DONE: Each page should represent the topicEach UI control (button, link) should be outlined andfunctional when clickedDemo – each team represents its module; Iana( customer) to accept the work

SCRUM – Exercise One. Two Three GO!

SCRUM – Exercise Sprint Retrospective:Did we make the Sprint? What went well What went not so well How to improve What to do in the next Sprint

SCRUM – Why it can failLack of commitment and reliability Incorrect time/work estimates Ineffective use of the retrospective Inability to get everyone on planning and daily meetings Bad Scrum Masters or Product Owners Lack of team authority and decision-making skills Team’s inability to learn State of denial

SCRUM – Limitations Project Scope: Scum is challenging for large complexprojects with geographically distributed teams anddifferent time zonesCannot be done in large teams and huge features(everything needs to be broken down)Requires good Scrum Masters and Product Owners – dowe have those?Some organizations require audit trail on everythingdone (military, medical) – need paperwork trail andproof

SCRUM – ConclusionScrum: Is doable and viable form of software developmentIs getting more and more popular in the fast pacing marketsDoesn’t require specific skills that could not be found or developedwithin the teamProduces stable product increments in short periods of timeMakes everyone in the team accountable for success or failure Develops great team spirit!

Backup slides

SCRUM - Exercise Run one Sprint for a project:“How to decorate a Christmas Tree”

SCRUM - Exercise 3-4 teams (5-6 people each) Within each team, define roles: Scrum Master (1) Product Owner (1) Team (3-4)

SCRUM – Exercise Select a page topic from Product backlog : Types of trees Where to get the tree Decorating with lights and toys Decorating with food Decorating with household items Last-minute decoration ideas Safety measures Do’s and Don’t’s in Christmas tree decorating

SCRUM – Exercise What to do in each team:Create a page (set of pages) on assigned topic Represent graphics and UI controls Can contain pictures/graphics (can you draw?) “Daily” Scrums! (every 15 mins) All pages should have consistent look and feel All pages should represent ONE site ( ScrumMasters/Product Owners should coordinate betweenthe teams on how pages are integrated and who isdoing the Main Page)

SCRUM – Exercise Definition of DONE: Each page should represent the topicEach UI control (button, link) should be outlined andfunctional when clickedDemo – each team represents its module; Iana( customer) to accept the work

Abnormally terminated Sprint: The Product Owner can cancel a Sprint if necessary with input from the team, scrum master or management. Management may wish to cancel a sprint if external circumstances negate the value of the sprint goal. If a sprint is abnormally terminated, the next step is to conduct a new Sprint planning meeting, where the

Related Documents:

Agile testing Agile testing can mean many kinds of testing: -Any testing that is not based on test case level plans. -Exploratory (sometimes called explorative) testing, where the tester proceeds based on his/her observations of the software. -Sometimes it means testing is agile software development.

1. The need for an agile way of working 6 2. The need for an agile way of working 9 3. Agile Core Values - Agile Project Management Vs. 10 Agile Event Management 4. Agile principles 12 _Agile Principles of Agile Project Management 13 _Agile Principles of VOK DAMS Agile Event Management 14 5. Agile Methods 16 _Scrum in Short 16 _Kanban in Short 18

After searching with the keywords: Agile testing software, Scrum agile testing software, Kanban agile testing software, Test Driven Development agile test software, Behavior Driven Development test software, automation test software, the tables 1, 2 and 3 show the number of scientific articles retrieved. This search was made with a restriction

The most popular agile methodologies include: extreme programming (XP), Scrum, Crystal, Dynamic Sys-tems Development (DSDM), Lean Development, and Feature Driven Development (FDD). All Agile methods share a common vision and core values of the Agile Manifesto. Agile Methods: Some well-known agile software development methods include: Agile .

Agile Estimating and Planning by Mike Cohn Agile Game Development with Scrum by Clinton Keith Agile Product Ownership by Roman Pichler Agile Project Management with Scrum by Ken Schwaber Agile Retrospectives by Esther Derby and Diana Larsen Agile Testing: A Practical Guide for Testers and Agile Teams by Lisa Crispin and .

AGILE TESTING For agile testers, test engineers, test managers, developers, technical leads. Ensure the production of effective and valuable software. Agile Fundamentals Agile Programming Agile Software Design Agile Fundamentals Agile Testing Agile Test Automation ICP CERTIFIED PROFESSIONAL ICP CERTIFIED PROFESSIONAL ICP-PRG CERTIFIED .

1.1 Purpose of the Agile Extension to the BABOK Guide1 1.2 What is Agile Business Analysis?2 1.3 Structure6 Chapter 2:The Agile Mindset 2.1 What is an Agile Mindset?7 2.2 The Agile Mindset, Methodologies, and Frameworks8 2.3 Applying the Agile Mindset9 2.4 Agile Extension and the Agile Ma

Agile World View "Agility" has manydimensions other than IT It ranges from leadership to technological agility Today's focus is on organizational & enterprise agility Agile Leaders Agile Organization Change Agile Acquisition & Contracting Agile Strategic Planning Agile Capability Analysis Agile Program Management Agile Tech.