• Save
Getting started with Agile
Upcoming SlideShare
Loading in...5
×
 

Getting started with Agile

on

  • 600 views

This presentation is about Agile Methodologies for delivering software. It explains how they were born, what motivated them, and why they work. We'll also take a look at how Agile can help you deliver ...

This presentation is about Agile Methodologies for delivering software. It explains how they were born, what motivated them, and why they work. We'll also take a look at how Agile can help you deliver a product of extreme complexity, with high quality levels, and with constant innovation by tapping into OutSystems' R&D case-study. Finally, we'll take a look ahead on the software lifecycle, and you'll learn how you can use Agile beyond development

Statistics

Views

Total Views
600
Views on SlideShare
592
Embed Views
8

Actions

Likes
0
Downloads
0
Comments
0

3 Embeds 8

http://paper.li 4
http://www.linkedin.com 3
https://www.linkedin.com 1

Accessibility

Upload Details

Uploaded via as Apple Keynote

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • Balancing Agility and Discipline: A Guide for the Perplexed\n
  • Balancing Agility and Discipline: A Guide for the Perplexed\n
  • Balancing Agility and Discipline: A Guide for the Perplexed\n
  • Balancing Agility and Discipline: A Guide for the Perplexed\n
  • Balancing Agility and Discipline: A Guide for the Perplexed\n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • Vision: A general idea for the app (as opposed to a rigid set of requirements)\nProduct Backlog: A list of requirements, sorted by priority\nIteration Backlog: The top most item of the backlog, that fits in an iteration\nIteration: Were dev magic occurs. Typically lasts 2 weeks.\nCustomer participation is paramount!\nPSP: Potentially shippable product\nBack to product backlog, that can change, with the participation of the customer.\n
  • Vision: A general idea for the app (as opposed to a rigid set of requirements)\nProduct Backlog: A list of requirements, sorted by priority\nIteration Backlog: The top most item of the backlog, that fits in an iteration\nIteration: Were dev magic occurs. Typically lasts 2 weeks.\nCustomer participation is paramount!\nPSP: Potentially shippable product\nBack to product backlog, that can change, with the participation of the customer.\n
  • Vision: A general idea for the app (as opposed to a rigid set of requirements)\nProduct Backlog: A list of requirements, sorted by priority\nIteration Backlog: The top most item of the backlog, that fits in an iteration\nIteration: Were dev magic occurs. Typically lasts 2 weeks.\nCustomer participation is paramount!\nPSP: Potentially shippable product\nBack to product backlog, that can change, with the participation of the customer.\n
  • Vision: A general idea for the app (as opposed to a rigid set of requirements)\nProduct Backlog: A list of requirements, sorted by priority\nIteration Backlog: The top most item of the backlog, that fits in an iteration\nIteration: Were dev magic occurs. Typically lasts 2 weeks.\nCustomer participation is paramount!\nPSP: Potentially shippable product\nBack to product backlog, that can change, with the participation of the customer.\n
  • Vision: A general idea for the app (as opposed to a rigid set of requirements)\nProduct Backlog: A list of requirements, sorted by priority\nIteration Backlog: The top most item of the backlog, that fits in an iteration\nIteration: Were dev magic occurs. Typically lasts 2 weeks.\nCustomer participation is paramount!\nPSP: Potentially shippable product\nBack to product backlog, that can change, with the participation of the customer.\n
  • Vision: A general idea for the app (as opposed to a rigid set of requirements)\nProduct Backlog: A list of requirements, sorted by priority\nIteration Backlog: The top most item of the backlog, that fits in an iteration\nIteration: Were dev magic occurs. Typically lasts 2 weeks.\nCustomer participation is paramount!\nPSP: Potentially shippable product\nBack to product backlog, that can change, with the participation of the customer.\n
  • Vision: A general idea for the app (as opposed to a rigid set of requirements)\nProduct Backlog: A list of requirements, sorted by priority\nIteration Backlog: The top most item of the backlog, that fits in an iteration\nIteration: Were dev magic occurs. Typically lasts 2 weeks.\nCustomer participation is paramount!\nPSP: Potentially shippable product\nBack to product backlog, that can change, with the participation of the customer.\n
  • Vision: A general idea for the app (as opposed to a rigid set of requirements)\nProduct Backlog: A list of requirements, sorted by priority\nIteration Backlog: The top most item of the backlog, that fits in an iteration\nIteration: Were dev magic occurs. Typically lasts 2 weeks.\nCustomer participation is paramount!\nPSP: Potentially shippable product\nBack to product backlog, that can change, with the participation of the customer.\n
  • Vision: A general idea for the app (as opposed to a rigid set of requirements)\nProduct Backlog: A list of requirements, sorted by priority\nIteration Backlog: The top most item of the backlog, that fits in an iteration\nIteration: Were dev magic occurs. Typically lasts 2 weeks.\nCustomer participation is paramount!\nPSP: Potentially shippable product\nBack to product backlog, that can change, with the participation of the customer.\n
  • Vision: A general idea for the app (as opposed to a rigid set of requirements)\nProduct Backlog: A list of requirements, sorted by priority\nIteration Backlog: The top most item of the backlog, that fits in an iteration\nIteration: Were dev magic occurs. Typically lasts 2 weeks.\nCustomer participation is paramount!\nPSP: Potentially shippable product\nBack to product backlog, that can change, with the participation of the customer.\n
  • Vision: A general idea for the app (as opposed to a rigid set of requirements)\nProduct Backlog: A list of requirements, sorted by priority\nIteration Backlog: The top most item of the backlog, that fits in an iteration\nIteration: Were dev magic occurs. Typically lasts 2 weeks.\nCustomer participation is paramount!\nPSP: Potentially shippable product\nBack to product backlog, that can change, with the participation of the customer.\n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • Things that can impact the speed:\n- Team\n- Type of project (UI, code only, ...)\n\n
  • Things that can impact the speed:\n- Team\n- Type of project (UI, code only, ...)\n\n
  • Things that can impact the speed:\n- Team\n- Type of project (UI, code only, ...)\n\n
  • Things that can impact the speed:\n- Team\n- Type of project (UI, code only, ...)\n\n
  • Things that can impact the speed:\n- Team\n- Type of project (UI, code only, ...)\n\n
  • Things that can impact the speed:\n- Team\n- Type of project (UI, code only, ...)\n\n
  • Things that can impact the speed:\n- Team\n- Type of project (UI, code only, ...)\n\n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • - 60/60 rule\n- Book is from 2002. This is bigger with Agile.\n- There are some challenges here: Getting things into production; Getting user feedback; Technical debt; Upgrading processes\n- But let’s focus on bug fixing\n
  • - 60/60 rule\n- Book is from 2002. This is bigger with Agile.\n- There are some challenges here: Getting things into production; Getting user feedback; Technical debt; Upgrading processes\n- But let’s focus on bug fixing\n
  • - 60/60 rule\n- Book is from 2002. This is bigger with Agile.\n- There are some challenges here: Getting things into production; Getting user feedback; Technical debt; Upgrading processes\n- But let’s focus on bug fixing\n
  • - 60/60 rule\n- Book is from 2002. This is bigger with Agile.\n- There are some challenges here: Getting things into production; Getting user feedback; Technical debt; Upgrading processes\n- But let’s focus on bug fixing\n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • - Team must be able to change its processes\n- Team must be eager do deliver value\n- Team must have a frequent and honest communication with customer\n- Collaboration within and beyond the team. Meetings != Collaboration\n- Never give up on quality\n- Small steps to everything\n- Automate the repetitive, error-prone time consuming tasks\n
  • - Team must be able to change its processes\n- Team must be eager do deliver value\n- Team must have a frequent and honest communication with customer\n- Collaboration within and beyond the team. Meetings != Collaboration\n- Never give up on quality\n- Small steps to everything\n- Automate the repetitive, error-prone time consuming tasks\n
  • - Team must be able to change its processes\n- Team must be eager do deliver value\n- Team must have a frequent and honest communication with customer\n- Collaboration within and beyond the team. Meetings != Collaboration\n- Never give up on quality\n- Small steps to everything\n- Automate the repetitive, error-prone time consuming tasks\n
  • - Team must be able to change its processes\n- Team must be eager do deliver value\n- Team must have a frequent and honest communication with customer\n- Collaboration within and beyond the team. Meetings != Collaboration\n- Never give up on quality\n- Small steps to everything\n- Automate the repetitive, error-prone time consuming tasks\n
  • - Team must be able to change its processes\n- Team must be eager do deliver value\n- Team must have a frequent and honest communication with customer\n- Collaboration within and beyond the team. Meetings != Collaboration\n- Never give up on quality\n- Small steps to everything\n- Automate the repetitive, error-prone time consuming tasks\n
  • - Team must be able to change its processes\n- Team must be eager do deliver value\n- Team must have a frequent and honest communication with customer\n- Collaboration within and beyond the team. Meetings != Collaboration\n- Never give up on quality\n- Small steps to everything\n- Automate the repetitive, error-prone time consuming tasks\n
  • - Team must be able to change its processes\n- Team must be eager do deliver value\n- Team must have a frequent and honest communication with customer\n- Collaboration within and beyond the team. Meetings != Collaboration\n- Never give up on quality\n- Small steps to everything\n- Automate the repetitive, error-prone time consuming tasks\n
  • - Much of it depends on you!\n- On your commitment\n- On your efforts to learn more\n- On your pledge to improve the quality of your work\n- On your courage\n- Agile only works with great teams. Great teams only work with great people. That means you!\n
  • \n

Getting started with Agile Getting started with Agile Presentation Transcript

  • Getting started with Agile
  • Waterfall
  • The idea
  • The ideaDesign
  • The ideaDesign Implementation
  • The ideaDesign Implementation Testing
  • The ideaDesign Implementation Testing
  • The idea Design Implementation TestingIdea
  • The idea Design Implementation TestingIdea Result
  • Release
  • ReleaseAx
  • ReleaseA Bx x
  • ReleaseA Bx x
  • ReleaseA Bx x B’ x
  • ReleaseA Bx x B’ x C x
  • ReleaseA Bx x B’ x What the business wants now! C x
  • The result? Succeeded Failed ChallengedFrom CHAOS Report 2009
  • The result? 32% Succeeded Failed ChallengedFrom CHAOS Report 2009
  • The result? 32% 20% Succeeded Failed ChallengedFrom CHAOS Report 2009
  • The result? 32% 49% 20% Succeeded Failed ChallengedFrom CHAOS Report 2009
  • This does not work!
  • Manifesto for Agile Software Development
  • Manifesto for Agile Software Development We are uncovering better ways of developing software by doing it and helping others do it. Through this work we have come to value:
  • Manifesto for Agile Software Development We are uncovering better ways of developing software by doing it and helping others do it. Through this work we have come to value:Individuals and interactions over processes and tools
  • Manifesto for Agile Software Development We are uncovering better ways of developing software by doing it and helping others do it. Through this work we have come to value:Individuals and interactions over processes and tools Working software over comprehensive documentation
  • Manifesto for Agile Software Development We are uncovering better ways of developing software by doing it and helping others do it. Through this work we have come to value:Individuals and interactions over processes and tools Working software over comprehensive documentation Customer collaboration over contract negotiation
  • Manifesto for Agile Software Development We are uncovering better ways of developing software by doing it and helping others do it. Through this work we have come to value:Individuals and interactions over processes and tools Working software over comprehensive documentation Customer collaboration over contract negotiation Responding to change over following a plan
  • Manifesto for Agile Software Development We are uncovering better ways of developing software by doing it and helping others do it. Through this work we have come to value:Individuals and interactions over processes and tools Working software over comprehensive documentation Customer collaboration over contract negotiation Responding to change over following a plan That is, while there is value in the items on the right, we value the items on the left more.
  • Manifesto for Agile Software Development We are uncovering better ways of developing software by doing it and helping others do it. Through this work we have come to value:Individuals and interactions over processes and tools Working software over comprehensive documentation Customer collaboration over contract negotiation Responding to change over following a plan That is, while there is value in the items on the right, we value the items on the left more. Kent Beck James Grenning Robert C. Martin Mike Beedle Jim Highsmith Steve Mellor Arie van Bennekum Andrew Hunt Ken Schwaber Alistair Cockburn Ron Jeffries Jeff Sutherland Ward Cunningham Jon Kern Dave Thomas Martin Fowler Brian Marick
  • Agile
  • AgileFeature 1
  • AgileFeature 1 Feature 2
  • AgileFeature 1 Feature 2 Feature 3
  • AgileFeature 1 Feature 2 Feature 3 Feature 4
  • AgileFeature 1 Feature 2• Design Feature 3• Implement• Test Feature 4
  • AgileFeature 1 Feature 2• Design Feature 3• Implement• Test • Design Feature 4 • Implement • Test • Design • Implement • Test • Design • Implement • Test
  • What’s the point? Design Implementation TestingFeature 1 Feature 2 Feature 3 Feature 4
  • What’s the point? Design Implementation Testing Ready to shipFeature 1 Feature 2 Feature 3 Feature 4
  • What’s the point? Design Implementation Testing Ready to shipFeature 1 Feature 2 Feature 3 Feature 4
  • What’s the point? Design Implementation Testing Ready to shipFeature 1 Feature 2 Feature 3 Feature 4
  • What’s the point? Design Implementation Testing Ready to shipFeature 1 Feature 2 Feature 3 Feature 4
  • What’s the point? Design Implementation TestingFeature 1 Feature 2 Feature 3 Feature 4
  • What’s the point? Design Implementation TestingFeature 1 Feature 2 Feature 3 Feature 4
  • What’s the point? Design Implementation Testing Feature 5Feature 1 Feature 2 Feature 3 Feature 4
  • What’s the point? Design Implementation Testing Feature 5Feature 1 Feature 2 Feature 3 Feature 4
  • What’s the point? Design Implementation TestingFeature 1 Feature 4 Feature 5 Feature 2
  • ReleaseA Bx x B’ x C x
  • ReleaseA Bx x B’ x C x
  • ReleaseA Bx x B’ x Demo! C x
  • ReleaseA Bx x B’ x Demo! C x
  • ReleaseA Bx x B’ x Demo! C x
  • Easy, isn’t it?
  • DependenciesFeature 1 Feature 4 Feature 5 Feature 2
  • DependenciesFeature 1 Feature 4 Feature 5 Feature 2
  • DependenciesFeature 1 Feature 4 Feature 5 Feature 2
  • DependenciesFeature 1 Feature 4 Feature 5 Feature 2
  • DependenciesFeature 1 Feature 4 Feature 5 Feature 2
  • Customer Feedback
  • Customer Feedback
  • Customer Feedback Just one more thing...
  • Customer Feedback Just one more thing... This is wrong!
  • Customer Feedback Just one more thing... This is wrong! Cool Stuff!
  • Customer Feedback Just one more thing... This is wrong! Cool Stuff! Found a bug!
  • Customer Feedback Just one more thing... This is wrong! Cool Stuff! Found a bug! While you’re at it...
  • Customer Feedback Just one Is it more important than more thing... the next feature? This is wrong! Cool Stuff! Found a bug! While you’re at it...
  • Customer Feedback Just one Is it more important than more thing... the next feature? This is wrong! Cool Stuff! Oops... we’ll fix it! Found a bug! While you’re at it...
  • Customer Feedback Just one Is it more important than more thing... the next feature? This is wrong! Cool Stuff! Oops... we’ll fix it! Found a bug! While you’re at it... Next version...
  • Customer Feedback Feature 2
  • Customer Feedback Feature 2 Feature 2
  • Project Delay? Design Implementation TestingFeature 1 Feature 4 Feature 5 Feature 2
  • Project Delay? Design Implementation TestingFeature 1 Feature 4 Feature 5 Feature 2
  • What gives?
  • What gives? Features WaterfallCost Schedule
  • What gives?Fixed Features Waterfall Cost Schedule
  • What gives?Fixed Features Waterfall Cost Schedule Variable
  • What gives?Fixed Features Cost Schedule Agile Waterfall Cost Schedule Features Variable
  • What gives?Fixed Fixed Features Cost Schedule Agile Waterfall Cost Schedule Features Variable
  • What gives?Fixed Fixed Features Cost Schedule Agile Waterfall Cost Schedule Features Variable Variable
  • Courage! From Agile in a Flash
  • Courage! • Quality work From Agile in a Flash
  • Courage! • Quality work • Make things simple From Agile in a Flash
  • Courage! • Quality work • Make things simple • Go for the hard problem From Agile in a Flash
  • Courage! • Quality work • Make things simple • Go for the hard problem • Architectural corrections From Agile in a Flash
  • Courage! • Quality work • Make things simple • Go for the hard problem • Architectural corrections • Throw away From Agile in a Flash
  • Courage! • Quality work • Make things simple • Go for the hard problem • Architectural corrections • Throw away • Only complete work From Agile in a Flash
  • Courage! • Quality work • Make things simple • Go for the hard problem • Architectural corrections • Throw away • Only complete work • Be transparent From Agile in a Flash
  • Not a silver bullet
  • Not a silver bullet Personnel
  • Not a silver bullet Personnel Team Size
  • Not a silver bullet Personnel Team Size Criticality
  • Not a silver bullet Personnel Team Size Criticality Dynamism
  • Not a silver bullet Personnel Team Size Criticality Dynamism Culture
  • About outsystems
  • About outsystems Since 2001
  • About outsystems Since 2001 199 Customers
  • About outsystems Since 2001 199 Customers 22 Industries
  • About outsystems Since 2001 199 Customers 22 Industries 59 Partners
  • About outsystems Since 2001 199 Customers 22 Industries 59 Partners 600+ Agile Projects
  • About outsystems Since 2001 199 Customers 22 Industries 59 Partners 600+ Agile Projects agileplatform™
  • agileplatform™ overview
  • agileplatform™ overview
  • agileplatform™ overview
  • agileplatform™ overview
  • agileplatform™ overview
  • agileplatform™ overview
  • agileplatform™ overview
  • agileplatform™ overview
  • Service Studio
  • Service Studio
  • Service Studio
  • Service Studio
  • Service Studio
  • Service Studio
  • The Application
  • 5 founders2 developers
  • BUFD
  • What was there?
  • What was there?• Visual Language
  • What was there?• Visual Language• Meta-model structure
  • What was there?• Visual Language• Meta-model structure• Platform Architecture
  • What was there?• Visual Language• Meta-model structure• Platform Architecture• Application Architecture
  • What was there?• Visual Language• Meta-model structure• Platform Architecture• Application Architecture• Security Model
  • What was NOT there?
  • What was NOT there?• Tools
  • What was NOT there?• Tools• Low Level Algorithms
  • What was NOT there?• Tools• Low Level Algorithms• Application Details
  • What was NOT there?• Tools• Low Level Algorithms• Application Details• User Interface
  • What was NOT there?• Tools• Low Level Algorithms• Application Details• User Interface• User Experience
  • What was NOT there?• Tools• Low Level Algorithms• Application Details ! ile• User Interface Ag st• User Experience lm o A
  • SCRUM
  • SCRUMVision
  • SCRUM ProductVision Backlog
  • SCRUM Product IterationVision Backlog Backlog
  • SCRUM Iteration Product IterationVision Backlog Backlog
  • SCRUM P.S.P. Iteration Product IterationVision Backlog Backlog
  • SCRUM P.S.P. Iteration Product IterationVision Backlog Backlog
  • SCRUM P.S.P. Iteration Product IterationVision Backlog Backlog
  • SCRUM P.S.P. Iteration Product IterationVision Backlog Backlog
  • Functional Teams
  • Functional Teams Server Team
  • Functional Teams Server Service Studio Team Team
  • Functional Teams Server Service Studio Team Team QA Team
  • Functional Teams Server Service Studio Team Team c t QA Team o je P r 1
  • Cross-functional Teams
  • Cross-functional TeamsProject A
  • Cross-functional TeamsProject A Project B
  • Cross-functional TeamsProject A Project BProject C
  • Cross-functional Teams DevProject A Project BProject C
  • Cross-functional Teams DevProject A Project B QAProject C
  • Cross-functional Teams Doc DevProject A Project B QAProject C
  • Cross-functional Teams Doc DevProject A Project B QAProject C Source Control
  • Cross-functional Teams Doc DevProject A Project B QAProject C Build & Test Source Control Automation
  • Burndown Charts
  • Missing Effort Burndown Charts
  • Missing Effort Burndown Charts Week
  • Missing Effort Burndown Charts Week
  • Missing Effort Burndown Charts Week
  • Burndown Charts Late!Missing Effort Week
  • Burndown Charts Late!Missing Effort Early Week
  • Missing Effort Burndown Charts Week
  • Burndown Charts TodayMissing Effort Week
  • Burndown Charts TodayMissing Effort Week
  • Burndown Charts TodayMissing Effort Week
  • Burndown Charts TodayMissing Effort Week
  • Burndown Charts TodayMissing Effort Week
  • Success
  • Success~30 people in R&D
  • Success~30 people in R&D16 major versions
  • Success~30 people in R&D16 major versions 543 updates
  • Success~30 people in R&D16 major versions 543 updates1.4M lines of code
  • Success ~30 people in R&D 16 major versions 543 updates 1.4M lines of code76,000+ tests running daily
  • Success ~30 people in R&D 16 major versions 543 updates 1.4M lines of code76,000+ tests running daily 20,295 installations
  • Beyond Development
  • The big effort... 40% 60% From Facts and Fallacies of Software Engineering
  • The big effort... Development 40% 60% From Facts and Fallacies of Software Engineering
  • The big effort... Development 40% 60%Maintenance From Facts and Fallacies of Software Engineering
  • The big effort... Development 40% 60%Maintenance From Facts and Fallacies of Software Engineering
  • Bug Fixing
  • Bug FixingTodo OnGoing Done!
  • Bug FixingTodo OnGoing Done!#12 @xpto UI
  • Bug FixingTodo OnGoing Done!#12 @Yai UI
  • Bug FixingTodo OnGoing Done!oh oh #12 @xpto Yai UI
  • Bug FixingTodo OnGoing Done!#12 oh oh @xpto Yai UI
  • Bug FixingTodo OnGoing Done!abc #12 @ oh ohxpto Yai UI
  • Agile Success Factors From Agile in a Flash
  • Agile Success Factors • Freedom to change From Agile in a Flash
  • Agile Success Factors • Freedom to change • Energized team From Agile in a Flash
  • Agile Success Factors • Freedom to change • Energized team • Communication with customer From Agile in a Flash
  • Agile Success Factors • Freedom to change • Energized team • Communication with customer • Collaboration From Agile in a Flash
  • Agile Success Factors • Freedom to change • Energized team • Communication with customer • Collaboration • Attention to quality From Agile in a Flash
  • Agile Success Factors • Freedom to change • Energized team • Communication with customer • Collaboration • Attention to quality • Incrementalism From Agile in a Flash
  • Agile Success Factors • Freedom to change • Energized team • Communication with customer • Collaboration • Attention to quality • Incrementalism • Automation From Agile in a Flash
  • You!
  • Thank you!rodrigo.coutinho@outsystems.com http://www.outsystems.com