• Save
rookie with zero bugs
Upcoming SlideShare
Loading in...5
×
 

rookie with zero bugs

on

  • 378 views

this is a checklist on how can we get a rookie developer to start working with zero bugs in the app

this is a checklist on how can we get a rookie developer to start working with zero bugs in the app

Statistics

Views

Total Views
378
Views on SlideShare
335
Embed Views
43

Actions

Likes
0
Downloads
0
Comments
0

4 Embeds 43

http://sdappsdev.outsystems.net 31
http://sdappsdev.domain.outsystems.com 8
http://www.linkedin.com 2
https://www.linkedin.com 2

Accessibility

Categories

Upload Details

Uploaded via as Microsoft PowerPoint

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
  • A interacção

rookie with zero bugs rookie with zero bugs Presentation Transcript

  • © outsystems – all rights reservedwww.outsystems.comwww.outsystems.comRookie with zero bugs
  • © outsystems – all rights reservedwww.outsystems.comwww.outsystems.comHow I got here?
  • © outsystems – all rights reservedwww.outsystems.comResearch &Development“we buildthe OutSystemsPlatform”ProfessionalServices“we delivery great appsusingthe OutSystems Platform”
  • © 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 #30Context
  • © outsystems – all rights reservedwww.outsystems.comwww.outsystems.comThe Challenge?
  • © outsystems – all rights reservedwww.outsystems.comdeliver great appshigh level of quality, performance andadopted by the end users
  • © outsystems – all rights reservedwww.outsystems.com• high level of quality• performance• and adopted by the end usersHow to address The Challenge?deliver great appsNOTNot AlwaysOK
  • © outsystems – all rights reservedwww.outsystems.com
  • © outsystems – all rights reservedwww.outsystems.comWherethe appsareGreat!Developersconfortzone
  • © outsystems – all rights reservedwww.outsystems.comWhat to do and where to start?1. Design and engage a Ramp UpPlan to speed up technologyknowledge2. Evaluate what are the main areas toimprove in the current team
  • © outsystems – all rights reservedwww.outsystems.comwww.outsystems.comLessons from thetrenches
  • © outsystems – all rights reservedwww.outsystems.com• Javascript and SQL were the main tech issues• Some significant number of bugs related withmeeting expectations with business
  • © outsystems – all rights reservedwww.outsystems.com• Start teaching Javascript and Advanced SQL inRamp up and it will solve all ourproblems...right?We are EngineersLet’s tackle the tech part
  • © outsystems – all rights reservedwww.outsystems.com
  • © outsystems – all rights reservedwww.outsystems.comThen we focus in...Remember the other one? Meetingexpectations with business
  • © outsystems – all rights reservedwww.outsystems.comwww.outsystems.comChecklist to zerobugs
  • © 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 storiesChecklist to zero bugs
  • © outsystems – all rights reservedwww.outsystems.com#1 Using User Stories instead of featuresContext iseverything, create a userstory.• Improves communication• Helps to learn the stakeholders “language”• Capture the reason why we’re delivering something.
  • © outsystems – all rights reservedwww.outsystems.comwww.outsystems.comBy understanding theusers, developers willstart thinkingdifferently
  • © outsystems – all rights reservedwww.outsystems.comWherethe appsareGreat!DevelopersconfortzoneProgressso far
  • © 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 userstories 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 userstories 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 ofthe code.
  • © outsystems – all rights reservedwww.outsystems.comWherethe appsareGreat!Progressso farDevelopersconfortzone
  • © outsystems – all rights reservedwww.outsystems.com#3 Doing Usability TestingWhy is so important developers participation in thedemos?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 thisDisclaimer: this doesn’t substitute user experience tests during the project, it’s anotheractivity to reach the goal of great apps.
  • © outsystems – all rights reservedwww.outsystems.comWherethe appsareGreat!DevelopersconfortzoneProgressso far
  • © outsystems – all rights reservedwww.outsystems.com#4 Acceptance Criteria for top userstories• Create the acceptance criterias for top userstories• Setup an environment with realistic sample data• This will help the business realize what theyreally need you to deliverStakeholders must test it!
  • © outsystems – all rights reservedwww.outsystems.comWherethe appsareGreat!DevelopersconfortzoneThe Teamdid it!!!
  • © 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 storiesChecklist to zero bugs
  • © outsystems – all rights reservedwww.outsystems.comwww.outsystems.comStart getting zerobugs from arookieThank Youhttp://www.slideshare.net/ricardonevesaraujo