rookie with zero bugs
0 likes746 views
This document outlines strategies used by a remote development team at OutSystems to improve quality and reduce bugs. The team initially struggled with technical issues like JavaScript and SQL. To address this, they implemented a ramp up plan to improve skills. However, they realized technical skills were not the only issue, as some bugs stemmed from not meeting business expectations. To solve this, the team introduced practices like using user stories instead of features to improve communication, defining acceptance criteria, conducting usability testing, and setting definitions for "ready" and "done". By applying these strategies, the team was able to progress out of their comfort zone and start delivering apps with zero bugs.
More Related Content
Similar to rookie with zero bugs (20)
![Strategic Picks — Prioritising the Right Agentic Use Cases [2/6]](https://cdn.slidesharecdn.com/ss_thumbnails/session-2-250902135931-4c97717a-thumbnail.jpg?width=560&fit=bounds)
rookie with zero bugs
- 1. © outsystems – all rights reservedwww.outsystems.comwww.outsystems.com Rookie with zero bugs
- 2. © outsystems – all rights reservedwww.outsystems.comwww.outsystems.com How I got here?
- 3. © outsystems – all rights reservedwww.outsystems.com Research & Development “we build the OutSystems Platform” Professional Services “we delivery great apps using the OutSystems Platform”
- 4. © outsystems – all rights reservedwww.outsystems.com • Remote Delivery Team @ Proença-a-Nova – Jan 2011 • #11 Developers • Age average 25 • Working experience ~ 1 year – Target to grow • Jan/2012 up to #20 • Jan/2013 up to #30 Context
- 5. © outsystems – all rights reservedwww.outsystems.comwww.outsystems.com The Challenge?
- 6. © outsystems – all rights reservedwww.outsystems.com deliver great apps high level of quality, performance and adopted by the end users
- 7. © outsystems – all rights reservedwww.outsystems.com • high level of quality • performance • and adopted by the end users How to address The Challenge? deliver great apps NOT Not Always OK
- 8. © outsystems – all rights reservedwww.outsystems.com
- 9. © outsystems – all rights reservedwww.outsystems.com Where the apps are Great! Developers confort zone
- 10. © outsystems – all rights reservedwww.outsystems.com What to do and where to start? 1. Design and engage a Ramp Up Plan to speed up technology knowledge 2. Evaluate what are the main areas to improve in the current team
- 11. © outsystems – all rights reservedwww.outsystems.comwww.outsystems.com Lessons from the trenches
- 12. © outsystems – all rights reservedwww.outsystems.com • Javascript and SQL were the main tech issues • Some significant number of bugs related with meeting expectations with business
- 13. © outsystems – all rights reservedwww.outsystems.com • Start teaching Javascript and Advanced SQL in Ramp up and it will solve all our problems...right? We are Engineers Let’s tackle the tech part
- 14. © outsystems – all rights reservedwww.outsystems.com
- 15. © outsystems – all rights reservedwww.outsystems.com Then we focus in... Remember the other one? Meeting expectations with business
- 16. © outsystems – all rights reservedwww.outsystems.comwww.outsystems.com Checklist to zero bugs
- 17. © outsystems – all rights reservedwww.outsystems.com #1 Using User Stories instead of features #2 Defining what’s Ready and what’s Done #3 Doing Usability Testing #4 Acceptance Criteria for top user stories Checklist to zero bugs
- 18. © outsystems – all rights reservedwww.outsystems.com #1 Using User Stories instead of features Context is everything, create a user story. • Improves communication • Helps to learn the stakeholders “language” • Capture the reason why we’re delivering something.
- 19. © outsystems – all rights reservedwww.outsystems.comwww.outsystems.com By understanding the users, developers will start thinking differently
- 20. © outsystems – all rights reservedwww.outsystems.com Where the apps are Great! Developers confort zone Progress so far
- 21. © outsystems – all rights reservedwww.outsystems.com #2 Defining what’s Ready and what’s Done • Is the definition of READY met for 70% of the user stories of next sprint? – should follow the INVEST principles – Acceptance criteria has been agreed with the customer – You have representative sample data • Have you met the definition of DONE for all user stories delivered in the Sprint? – Test each user story against the acceptance criteria – and other tests defined in the test plan – may also include conducting automated or manual code reviews over a part of the code.
- 22. © outsystems – all rights reservedwww.outsystems.com Where the apps are Great! Progress so far Developers confort zone
- 23. © outsystems – all rights reservedwww.outsystems.com #3 Doing Usability Testing Why is so important developers participation in the demos? Usability tests start during the first Demo • 1st reactions are the most genuine • Usually there’s Feedback...tons of it • You don’t need extra budget to this Disclaimer: this doesn’t substitute user experience tests during the project, it’s another activity to reach the goal of great apps.
- 24. © outsystems – all rights reservedwww.outsystems.com Where the apps are Great! Developers confort zone Progress so far
- 25. © outsystems – all rights reservedwww.outsystems.com #4 Acceptance Criteria for top user stories • Create the acceptance criterias for top user stories • Setup an environment with realistic sample data • This will help the business realize what they really need you to deliver Stakeholders must test it!
- 26. © outsystems – all rights reservedwww.outsystems.com Where the apps are Great! Developers confort zone The Team did it!!!
- 27. © outsystems – all rights reservedwww.outsystems.com #1 Using User Stories instead of features #2 Defining what’s Ready and what’s Done #3 Doing Usability Testing #4 Acceptance Criteria for top user stories Checklist to zero bugs
- 28. © outsystems – all rights reservedwww.outsystems.comwww.outsystems.com Start getting zero bugs from a rookie Thank You http://www.slideshare.net/ricardonevesaraujo
Editor's Notes
- #19: A interacção