More Related Content
![Acid rain powerpoint presentation[1]](https://cdn.slidesharecdn.com/ss_thumbnails/acidrainpowerpointpresentation1-130522105428-phpapp02-thumbnail.jpg?width=640&height=640&fit=bounds)
Smart
- 1. Be Smart! or What they don’t teach you about software at school Ivar Jacobson with Ian Spence, Pan Wei Ng and Kurt Bittner ivar@ivarjacobson.com www.ivarblog.com
- 2. Your goal isthe same as always! Good Software Good Software, Quickly and at Low Cost! © 2008 Ivar Jacobson International 2
- 3. What it takes Quickly Competent & Motivated People Low Cost Large Scale Reuse of Components Good Software Useful Extensible Reliable © 2008 Ivar Jacobson International 3
- 4. What it takes Quickly What they don’t Competent & Motivated People teach you about Low Cost Large Scale Reuse of Components software at school Useful ☺ Good Software Extensible Reliable
- 5. One major obstacle…weare a fashion industry Software Development is driven by fashions and fads – Fifteen years ago it was all about OO – Ten years ago it was about components, UML, Unified Process – Five years ago it was about RUP and CMMI – Two years ago it was about XP – Today it is about Scrum All good, but none is all you need This is unsmart! The software industry keeps looking for a silver bullet © 2008 Ivar Jacobson International 5
- 6. One major obstacle…weare a fashion industry Yes, Software Development is driven by fashions and fads – Fifteen years ago it was all about OO – Ten years ago it was about components, UML, Unified Process – Five years ago it was about RUP and CMMI – Two years ago it was about XP – Today it is about Scrum All good, but none is all you need This is unsmart! The software industry keeps looking for silver bullets © 2008 Ivar Jacobson International 6
- 7. One major obstacle…weare a fashion industry Yes, Software Development is driven by fashions and fads – Fifteen years ago it was all about OO – Ten years ago it was about components, UML, Unified Process – Five years ago it was about RUP and CMMI – Two years ago it was about XP – Today it is about Scrum All good, but none is all you need This is unsmart! The software industry keeps looking for silver bullets © 2008 Ivar Jacobson International 7
- 8. Agenda 1. What does Smart mean? 2. Smart Cases – Recognize it when you see it 3. How do you become Smart 4. What does Smart really mean? © 2008 Ivar Jacobson International 8
- 9. What does Smartmean? Things should be done as simple as possible – but no simpler - Albert Einstein E= mc2 This is smart! © 2008 Ivar Jacobson International 9
- 10. Smart and Intelligent? •Being Smart is not the same thing as being intelligent – You can be intelligent without being smart, and – You can be very smart without being very intelligent Mr Smart © 2008 Ivar Jacobson International 10
- 11. Smart and Agile? •Being Smart is an evolution of Being Agile – Agile means being flexible and adaptable. – Agile provide simple/lightweight starting points – But being smart is knowing when to go beyond agile • Knowing when to follow the rules and when to break them • Knowing when to be consistent and when to change • Knowing when to grow and when to shrink Mr Smart Smart = Agile ++ © 2008 Ivar Jacobson International 11
- 12. Everyone is Agile! • Agile is in Everything! • Agile’s origin is social engineering – Now everything good in software development has become agile • Scaling agile – Picking the low hanging fruits of agile – Getting the dramatic effects with agile • Practices are the tool to scale – There are practices and Practices – Practices made practical – Our precise practices are as simple as possible – but not simpler – Precise practices change the whole concept of process © 2008 Ivar Jacobson International 12
- 13. Agenda 1. What does Smart mean? 2. Smart Cases – Recognize it when you see it 1. People 2. Teams 3. Projects What they don’t 4. Requirements teach you 5. Architecture 6. Modeling about software 7. Test at school 8. Documentation 9. Process 10.Knowledge ☺ 11.Outsourcing 12.Tools 3. How do you become Smart 4. What does Smart really mean? www.ivarblog.com © 2008 Ivar Jacobson International 13
- 14. Not smart withPeople Some companies view process and tools as more important than people This is unsmart! A fool with a tool is still a fool but a dangerous fool © 2008 Ivar Jacobson International 14
- 15. Smart with People Case study: Ericsson AXE – the largest commercial success story ever in Sweden –We had no tools and no defined process –Despite this, we developed components, use cases, and a modeling language now part of UML –This could only have been done with people – good people Software is developed by people, This is smart! not by process and tools. © 2008 Ivar Jacobson International 15
- 16. Not smart withTeams • Many software projects involve 20+ people • Often organized into stove-pipe groups: – Requirements, Analysis, Design, Coding, Testing, etc. This is unsmart! Requirements Implementation Test © 2008 Ivar Jacobson International 16
- 17. Smart with Teams • Teams are cross-functional Including analysts, developers, testers etc… • Ideal size of the team is less than 10 people This is smart! A software team is like a sport team with all needed competencies to win. © 2008 Ivar Jacobson International 17
- 18. Not smart withProjects • Most companies still follow the waterfall approach Requirements High-Level Design Detailed-Level This is unsmart! Design Coding Crash! Testing © 2008 Ivar Jacobson International 18
- 19. Smart with Projects • Build a skinny system to demonstrate that you have eliminated all critical risks • Add more capabilities on top of that skinny system This is smart! Skinny System Full Fledged System Think big, build in many steps © 2008 Ivar Jacobson International 19
- 20. Not smart withRequirements • Many managers (and customers) believe you can detail all the requirements upfront... • ...and based on these can accurately predict the cost of the solution Thou shalt work with fixed requirements for fixed prices This is unsmart! A constant in software development is that requirements always change © 2008 Ivar Jacobson International 20
- 21. Smart with Requirements • Base early decisions on lightweight requirements and detail as and when it is needed – Use case outlines, feature lists or user stories • Remember requirements are negotiable and priorities will change This is I understand your needs, let’s work smart! together to make sure we develop the right system for the right price. Design your project for requirement changes © 2008 Ivar Jacobson International 21
- 22. Not smart withArchitecture Two extremes: Mr Enterprise Architect on Ivory Tower No architecture Just Code Refactor later I’ll design everything up front This is unsmart! Mr Supposedly Agile The single most important determinant of a software system’s quality is the quality of its architecture © 2008 Ivar Jacobson International 22
- 23. Smart with Architecture • Focus on the skinny system • But an architecture without executable code is a hallucination • Refactor over releases, but large refactoring is very costly Architectural Blue Print Skinny System Full Fledged System Start to build a skinny system, This is add muscles in later steps smart! © 2008 Ivar Jacobson International 23
- 24. Not smart withTest We have two classes of people: Developers and Testers – Developers are the creators…it is OK to create bugs as well – Testers are the cleaners in the software world Testing is done as an after thought – too late and too expensive This is unsmart! © 2008 Ivar Jacobson International 24
- 25. Smart with Test We are all testers ! This is smart! Whatever you do you are not done until you have verified that you did what you wanted to do © 2008 Ivar Jacobson International 25
- 26. Not smart withDocumentation • There has been an over-emphasis on teams producing documentation Thou shalt follow the document template I give you to document every part of This is unsmart! the system. © 2008 Ivar Jacobson International 26
- 27. Smart with Documentation Myth: The idea that you document software so people later can read what you did. – Law of nature: People don’t read documents This is smart! Focus on the essentials - the placeholders for conversations – people figure out the rest themselves © 2008 Ivar Jacobson International 27
- 28. Not smart withProcess/Methodology/Approach Agile CMMI Unified CMMI Process Existing Way of Working Project Lead © 2008 Ivar Jacobson International 28
- 29. Not smart withProcess/Methodology/Approach Agile CMMI Unified CMMI Process Existing Way of Working Project Lead © 2008 Ivar Jacobson International 29
- 30. Not smart withProcess/Methodology/Approach Agile CMMI Unified CMMI Process I want a new way of working New Way of Working Project Lead © 2008 Ivar Jacobson International 30
- 31. Not smart withProcess/Methodology/Approach We have got enough of process Agile Unified CMMI Process I like to have Let me start some to I want of have with Agile, unified some of CMMI maybe process Does notget it I cannot together work New Way of Working This is unsmart! Project Lead © 2008 Ivar Jacobson International 31
- 32. Smart with Process/Methodology/Approach Existing Way of Working Don’t throw out your baby with the bathwater: 1. start from your existing way of working, 2. find your pain points, and 3. change one practice at the time. © 2008 Ivar Jacobson International 32
- 33. Smart with Process/Methodology/Approach And the Law of Nature: People don’t read process books So focus on the essentials, people figure out the rest themselves New Way of This is Working smart! Don’t throw away your baby with the bathwater: 1. start from your existing way of working, 2. find your pain points, and 3. change one practice at the time. © 2008 Ivar Jacobson International 33
- 34. Agenda 1. What does Smart mean? 2. Smart Cases – Recognize it when you see it 3. How do you become Smart 4. What does Smart really mean? © 2008 Ivar Jacobson International 34
- 35. Summary: Key Elementsto Smart Cases • People: Software is developed by people, not by process and tools. • Teams: A software team is like a sport team with all needed competencies to win. • Project: Think big, build in many steps. • Requirements: Design your project for requirement changes. • Architecture: Start to build a skinny system, add muscles in later steps. • Modeling: Don’t duplicate the effort by modeling everything • Testing: Whatever you do you are not done until you have verified what you wanted to do. • Documentation: Focus on the essentials - the placeholders for conversations – people figure out the rest themselves • Process: Don’t throw away your baby with the bathwater: 1. start from your existing way of working, 2. find your pain points, and 3. change one practice at the time. © 2008 Ivar Jacobson International 35
- 36. How do youbecome Smart? • You need knowledge in good (maybe best) practices – There are 100’s of practices, some of them are good Business Test-Driven Scrum Product-Line Risk-Driven Systems Modeling Development Engineering Iterative Engineering Development Aspect Robustness Retro- Business Process Use-Case Pair Orientation Analysis spectives Re-Engineering Driven Development Programming PSP User Stories SOA Prince2 Use-Case Program Modeling Management • And you need experience in using them © 2008 Ivar Jacobson International 36
- 37. Agenda 1. What does Smart mean? 2. Smart Cases – Recognize it when you see it 3. How do you become Smart 4. What does Smart really mean? © 2008 Ivar Jacobson International 37
- 38. What does Smartreally mean? • If you didn’t get what smart is so far let me summarize it to you © 2008 Ivar Jacobson International 38
- 39. Of course, eventuallyit comes back to you, but We can all become smarter. © 2008 Ivar Jacobson International 39
- 40. Thank You Contact me at ivar@ivarjacobson.com © 2008 Ivar Jacobson International 40