![Why don't small companies do Agile? ,[object Object],[object Object],[object Object]](https://image.slidesharecdn.com/smallcompanyagile-jax-110411160132-phpapp02/85/why-dont-small-companies-do-big-a-agile-1-320.jpg)
![Small Company ,[object Object]](data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7)
Recommandé
Contenu connexe
Tendances
Tendances (20)
Similaire à Why small companies don't need big Agile processes
Similaire à Why small companies don't need big Agile processes (20)
Dernier
Dernier (20)
Why small companies don't need big Agile processes
- 7. Management imposed – top down agile
- 11. What makes a small company little a agile?
- 17. If any test coverage, devs likely to setup unasked
- 20. Need to recognise revenue
- 21. Demoable product to drive sales
- 22. Learn & iterate
- 23. What stops a company being agile?
- 30. Releasing an increment involves multiple teams
- 34. Different priorities: new features, support, technical
- 35. Team ends up ”thrashing”
- 43. ” A large company adopts agile to behave
- 44. more like a small company”
- 45. A company only needs formal Agile Adoption if it isn't naturally agile
- 47. What does “Doing Agile” look like?
- 51. No story point standard
- 53. Let team solve design problems up front
- 55. Best if expected velocity “reverse engineered”
- 63. -- Bob Martin
- 69. “ Just enough” process
- 70. Producing high quality product
- 72. Deliver an increment of software independently
- 73. Minimize number of dependencies
- 74. Productive partnership with customer
- 77. Best developers writing code, not managing
- 78. More developers ≠ faster
- 79. Avoid “dead sea effect”
- 81. Process should be internal to team
- 84. -- Bob Martin
- 86. Schedule implied
- 87. Cut features not corners
- 91. TDD / ATDD / BDD
- 93. Small releases
- 94. Coding standards
- 97. Product owner
- 98. Daily scrum
- 99. Sprint planning
- 100. Sprint review
- 101. Sprint retrospective
- 105. Better developers over more developers
- 107. Quality over crap
Notes de l'éditeur
- Java developer Agile enthusiast Aspiring software craftsman Co-founder of LSCC Twitter Why don't small companies do Agile?
- Start with some definitions Tried doing by numbers About names not roles ” We need Mike to help with this” ” That's a job for Rachel” In large co ” We need QA to help with this” ” That's a job for the operations team” Not to say ppl don’t know each other Identifying by role/team creates short hand – but creates barrier
- We mean agility Responsiveness; ability to react Bottom up – enthusiastic developers introduce specific practices
- Agile goes mainstream Big-A-Agile is how we try to get there
- Take away the theatre and buzzwords – agility is pretty simple Iterate!
- XP practices fit this perfectly Scrum & kanban provide structure on top – forecasting, planning & process improvement
- BA vs talking direct to customer Requirements review; architecture standards committee; design sign-off Not been in business long Large business, older, more time to build legacy Interesting metric: LOC/developer 50k 10ppl = 5k/dev 1m 20ppl = 50k/dev Large companies, more code & more code per-developer More to remember Harder to change Software factory
- With less inventory, even starting on wrong foot easier to retro-fit tests Dev owns junit tests; BA owns acceptance tests; who owns browser tests? QA or dev? What if they're written in junit?
- Small company trying to find product market fit – can’t wait
- So small companies naturally do something approximately agile; what stops a large company replicating that?
- Byzantine process – dedicated job to navigate Failure of an alternative, nervous management return to process safety net “ We’re doing agile, but...” Requirements review, design sign off This isn’t “scrum, but” – its “waterfall, but we’re pretending its agile”
- Separate QA, build, operations team More people, more meetings, more waste
- Everybody ”does their job”, instead of delighting the customer ” I fixed the bug, it's up to QA to test it” ” I raised the defect, I'm waiting for dev to fix it” ” The build's ready, operations need to deploy it” ” It's the maintenance team's job to fix bugs” Thrashing - reviewing possibilities / changing direction
- Development is documenting requirements Start from vague ideas; most precise form is code Project idea has a lot of appeal – but software is weird stuff People feel threatened by agile
- So why do large companies do big A Agile... Or the stupid...
- Coming from waterfall background, or half arsed agile
- What would a diabolical agile roll out look like? How would Dilbert's PHB do it?
- Project mindset Have team size, fixed scope, fixed date Backlog full of mandatory stories Extra credit: new to company
- Alpha geek & passive-aggressive cynic Solve all design problems – can't estimate without understand what we're building Everything is a 5 anyway Might feel like planning theatre, but its important to be able to hold developers accountable for their commitment
- Sprint end – stories not done carry over Process set in stone, can't change it But of course, this isn't agile – it's a checklist of behaviours
- Now agile is mainstream First line of the agile manifesto Ironically...
- If big-A-agile isn’t the answer for large companies, perhaps software craftsmanship provides a better view?
- Software craftsmanship typically focuses on the individual developer How can I improve? How can I learn? How can I mentor others? I’d like to go off in a slightly different direction – if I built a team of craftsmen, what would that look like
- Responsible for, and capable of , delivering a working increment More dependencies, more project management Developers want to understand the business Let them work with the customer, not for the customer
- Bob Martin talks about 1 master, 3 journeymen, 9 apprentices Fred Brooks “If a 200 man project has 25 managers who are the most competent and experienced programmers, fire the 175 troops and put the managers back programming”
- If team responsible for customer to production; all process is internal to team Conforming to standard should be choice of team – because it’s beneficial to the team Some mandatory – rest owned by team
- Most developers need to work harder on improving quality; very few over-engineer Rush design, multiple code rewrites Skip unit testing, bugs found late – expensive to fix. Not my fault – unlucky Bugs thrive in crap code; debugging crap code takes time -> just fix the code! Scrum/kanban etc give ways of tracking velocity/cycle time to make projections based on past experience If schedule is slipping, cut features not corners
- So how does craftsmanship help?
- Developers understand the business; customer trusts the development team -> what to build next. Small, autonomous team; with right experience; producing clean code -> implement smallest thing One team (devops); minimal, self-improving process; working in partnerhsip with the customer -> get feedback quickly On top of the XP practices, craftsmanship is about the relationships, the team structure and a focus on quality
- XP is about the day-to-day practices What developers do
- Scrum is about the iteration-by-iteration practices What project managers do
- Software craftsmanship is about developers “raising the bar” But it’s also about building the right team and genuinely empowering them to craft great software This is in management ’s domain Craftsmanship has these four key goals to enable agile delivery: autonomy, experience, process & quality – let me summarise my thoughts about this into what I think the software craftsmanship manifesto should have said
- We don’t want dependencies, scheduling and project management – we want autonomy We don’t want armies of untrained developers – we want to hire great developers with a balance of experience and help them all progress We don’t want long process definition documents – we want permission to use the right process for the job Finally, we have to stop writing crap thinking its quicker. If we do the job right, speed will come naturally.