The Agile Mindset
- 1. The Agile Mindset Tony Caniglia
- 2. Introduction • Waterfall SDLC Refresher • Industry Disrupt • Highlight Waterfall challenges in delivering software applications • How Agile improves on Waterfall • Share some Agile success stories • Overview a Agile Scrum practice
- 3. BIO • Software Engineer • Developing applications for Vertical/Niche markets • Waterfall • Java Instructor • Enterprise Java Architect • Agile • Business Process Analyst (automated business process) • Solutions Architect • Senior Consultant with GLASS
- 4. Agile Background • I Reviewed an Agile implementation • Reviewed and provided my feedback to the business • I Recommended Agile and the technology for an Enterprise uplift Proposal • We were warded the contract • I carried out the Agile and technology implementation • Participated in a several Agile projects later • Continue to research and skill up in Agile and Lean
- 5. Waterfall
- 6. Waterfall Process • Waterfall SDLC (Software Development Life Cycle) • Review Waterfall Activities and Artefacts • Requirements Management • Communication/Collaboration • Planning (Project Management) • Estimating • Reporting
- 7. Waterfall SDLC - stages Analysis Design Development Testing Deploy Requirements Product
- 8. Waterfall SDLC - collaboration Analysis Design Development Testing Deploy
- 9. Requirements Management • Identify all the requirements up front (try) • Document • Requirements • Functional/Non-Functional • Design Document • Sign off • Add traceability • Define the Scope of the Project
- 10. Waterfall Project • Requirements • Define Scope • Estimate Cost based on Scope • Use Scope and Cost to Plan and resource project • Signoff and agreement • Deliver Project by the end date
- 11. Estimate Algorithms 1. Sum up all requirements • Pad a couple of months • Double it 2. Most Accurate estimate • Determine length of a piece of string • Lol
- 12. Project Plan – key dates Middle Date(s) Start Date End Date
- 13. Waterfall Reporting • Generally done by Project group • Using Gant Charts • Other tools • Progress measured against • Milestones Dates • Project End date
- 15. Waterfall Era • Worked Well ! • Good fit • People • Process • Technology
- 16. Question • When was this era and what was the technology?
- 17. Mainframes and Mini computers
- 19. Disrupt • PC • Object Oriented Languages • Internet
- 20. Technology Disrupt • Personal Computer • More options • Limitless capability
- 21. Technology Evolving Rapidly • Increased Market opportunities • Less time to develop and release products to market • Challenges • More Requirements • More technology options • More Scope
- 22. Waterfall Challenges • Requirements defined at the start • One big release at the end • Moveable target dates • Work was assigned to teams • Development tools lacked required functionality • Increased time to use • Scope Creep!
- 24. How do you solve Scope Creep? 1. Freeze Requirements • Release the product to market • Staged Releases of the product from the added requirements 2. Implement Heavy Change Control Process • More documentation • More meetings • Add an Emergency Rule Loophole
- 25. Recap • Product delivered at end of project • Requirements change or added very late in the delivery • Required a lot of rework • Documents • Sign offs • Agreements from various levels
- 26. Rapid Application Development (RAD)
- 27. UML • Unified Modelling Language (UML) • Object Oriented Analysis (OOA) • Object Oriented Design (OOD) • Object Oriented Programming (OOP)
- 28. Rational Unified Process (RUP) Heavyweight Process
- 29. Agile Practice
- 30. Quote • Scrum is • Lightweight • Easy to understand • Difficult to master • Sourced from scrum.org
- 31. Scrum Events • Sprint Planning • What can be delivered within the Sprint • Sprint • Time boxed iteration • Daily Scrum (stand up) • Sprint Review • Close Sprint • Sprint Retrospective
- 32. Scrum Artefacts • Product Backlog • Sprint Backlog • Increment (MVP)
- 33. Scrum Roles • Product Owner (requirements) • Scrum Master • Development Team
- 34. Agile Management Tools • Agile Management Tool • Version One • JIRA • Microsoft TFS • CA • Manually Manage
- 35. Product Backlog • Repository for all unplanned backlog items • Backlog item is either • User Story • Task
- 36. User Story • User stories save on from writing about requirements to talking about them. • “Flexible requirements” • Define Scope
- 37. User Story format • As a < type of user >, I want < some goal > so that < some reason >. • Example: As a customer, I would like to see my account balances so that I know how much money is in my accounts • Tasks • Add Tasks to User Story • Assist with tracking work • Assign estimates to either the User Story or the Tasks
- 38. Features • Features a Group of User Stories • Features span sprints • Features help to measure progress
- 39. Sprint Backlog • Created from the Product Backlog • Move Backlog item from Product backlog to Sprint backlog • Plan only what you can complete in a Sprint
- 41. Showcase • Show Minimal Viable Product (MVP) • Why? • Definition of Done • Possibly Identify more Requirements
- 42. Question: Time boxed Iteration • Sprint is a timeboxed iteration with a start and end date. • Can you change the length of the Sprint after you start it, (end date) • A) No • B) Yes • C) all of the above
- 43. My Introduction to Agile • Review Agile XP implementation • Team received consulting, training and coaching in Agile XP • Generalisation of Agile implementation • Morning meeting everyone stands and talks about what they are going to do • Two Developers working together • Do little or no design or documentation
- 44. Before going Agile • Struggled to get a working build out • Long development cycles • Planning took a long time and wasn’t effective • Looking to blame someone
- 45. After Agile • Regular working releases • Increased test coverage and regression testing • Regular Showcases with Stakeholders • Deployed a working product into production • And subsequent releases into production
- 46. Successful Agile XP • Successful Agile Implementation, because • People • Received consulting and coaching in Agile XP • Process • Teams shared common Agile XP • Technology • Java IDE with refactoring capability • Spring Web frameworks (modularity) • Auto build, test and deploy servers • :
- 47. My 2nd Agile experience Recommended the Technology solution and Agile for the delivery approach And oversaw the implementation Used my learning from the 1st Agile review
- 48. My Agile Recommendation • Recommended Agile & Technology for a Enterprise uplift Bid • Agile Scrum • Enterprise Java Web Application architecture • Java IDE and tools enhanced productivity • Automation tools • Source code, Test, Build and Deploy • Continuous Integration (CI), Continuous Deployment (CD)
- 49. Missing parts Technology Commercial IDE (JetBrains) , Automation tools, etc People Process
- 50. Hired 3 Skilled resources • Provided the hiring criteria • Java Web Development • Test Driven Development • Agile experience
- 51. Increased Success factor Technology People Process Agile Tool Version One
- 52. Agile Tool • USA partner requested project visibility • Recommended - Version One SaaS
- 53. Version One • SaaS – no installation required • Up and running in under 2 days • Configured • Agile Scrum methodology (practice) • 2 week iterations
- 54. Our Sprints
- 55. Sprint Planning • Self Organising Teams • Team members selected the backlog item(s) t • and estimated it • We used Backlog item (task)
- 56. Estimating Backlog item • Backlog Item • Functional requirement • Effort based estimates • 1 point = 1 day
- 57. Daily Scrum (stand up) • What did I do yesterday • What will I do today • Do I know of any impediments • Usually finished under 5 minutes • Updated Version One daily
- 58. Sprint Review • We strived to complete all tasks • Uncompleted Task • Split tasks ( Version One auto handled ) • Note: All tasks in Sprint Backlog completed or moved to Backlog
- 59. Burndown chart
- 60. Showcase • Showcase end of Sprint • We had Continuous Deployments • Stakeholders had to deployments
- 61. Summary • Waterfall Refresher • Overviewed of Agile Scrum events and artifacts • Shared some successful Agile Projects
- 62. Questions
- 63. Contact Details • email • Tony Caniglia@glassandco.com.au • LinkedIn • www.linkedin.com/in/tony-caniglia
Editor's Notes
- #50: Worried it was going to fail and could easily Jet Brains