building a better team web

8/9/2019 Building a Better Team Web

1/26

Building a Better Team

As your team grows and evolves so do some of your development problems. Mostdevelopment teams struggle as they grow and try to implement top-down processes

that dont always work well with developers. This presentation will guide you through

proven steps and techniques to bring an unstructured development environment into a

cohesive unit. The processes discussed will help you and your team develop better code,

reduce development costs, and build better applications. The techniques discussed in

this presentation have been successfully implemented at various organiations and have

helped both A!"# and !$%&'$ teams.

(


2/26

)T* and )o-founder at )lari+it http%%www.)lari+it.com

Author of *racle A!"# blog http%%www.TalkApe.com

irector for *racle evelopment Tools /ser 0roup 1*T/02 http%%www.odtug.com *racle A)" irector

3


3/26

4eginning *racle Application "press 5 http%%goo.gl%67o+

"pert *racle Application "press http%%goo.gl%t#m8!

More info about this bookhttp%%9es.blogs.shellprompt.net%3:((%:8%8:%epert-oracle-application-

epress

"pert *racle Application "press !lugins http%%goo.gl%:;


4/26

)lari+it is a *racle A!"# and !$%&'$ consulting and training firm based out of )algary,

Alberta, )anada

+or more information please visit http%%www.)lari+it.com or email info=)lari+it.com

5


5/26

)oding &tandards usually have the following issues

>ritten a long time ago by someone that may or may not still work in organiation 4ecause of this no one understands why certain standards are in place

ry read that is usually read once and never referenced again

6ot updated

?


6/26

@ules 0uidelines

@ule +ollow (::B of the time 0uideline +ollow


7/26

@ules 0uidelines Template

All @0 are created with this template +irst two fields are required

Make sure @0 is an Active voice sentence

@emoves any ambiguity

" 1incorrect2 ont use us upper case values for key words

&o are Select, SeLeCt, E valid optionsF

" 1correct2 Gey words are lowercase

This leaves no opening for a different interpretation

Geep the @%0 and >hy to one or two lines

@0 final document consists of many of these @0 grouped together

H


8/26


9/26

+or code samples try to highlight the code area by bolding it. 4y doing this it allows

readers to know eactly what the @0 is discussing.


10/26

Cmplementation is an easy thing to do. The following IagendaJ is a good one to start

with and modify accordingly

&chedule ( hour meetings with your team for a month two

uring the first meeting eplain what @0 are etc.

)ome prepared with a set based on your current coding IstandardsJ

7ave the team vet all of them. Kou may find new cases come up etc.

4y having the team agree to the @0 you have buy in since they all

participated

Cf theres a tie you, as document master, need to make final decision

7ave team consistently send you new @0 they want to see included in the

document which you include for each meetings discussion

"ventually you wont need to meet once a week. )hange to once a month.

+inally all youll need to do is meet once a quarter

(:


11/26

)ode reviews are not tough to do. The biggest challenge is cultural and political

7istorically developers hate having someone else look at their code

0ive eample of civil engineers and bridge building. All bridge designsget thoroughly reviewed before they are built. Cf they were built with

the same methodology developers 1i.e. no one sees design2 then

theyd all fall apart

Managers question the time

3 things happen with code reviews

)ross training

4usiness functionality

Technical skill set

@eduction in small bugs which will save time%money%quality etc 1more

on this in net sets of slides2

7istorically

- evelopers hate them

- Management doesnt like them

- 6o one has fun

- Talk about the advantages

- )ross Training

- $earn from other developers

- )onsistency

((


12/26

&afety triangle used in large organiations to help reduce in9uries and fatalities

(3


13/26


14/26

4y reducing the bottom layer 1i.e. the small mistakes2 the end result is that you reduce

fatalities

(5


15/26

- &tory on *il 0as pipeline worker

- &ummary Cssues usually occur because a small thing was missed or process wasnt

followed. 6eed to focus on those small things

(?


16/26

&afety triangle for software development

(D


17/26


18/26

4y reducing the bottom layer 1i.e. the small mistakes2 the end result is that you reduce

system downtime and lost costumers.

(;


19/26

0et buy in from management

6ot always easy to do but use business reasons listed in )ode @eview intro

slide @elate reasons in terms of how the business will do better

evelopers

"plain the value of code reviews

Accountability

Cf person A reviews person 4s code, they are as responsible for the

outcome of the code

Though harsh, this technique avoids people doing a quick scan and

passing reviews

7ave a random round robin approach for reviewing code

i.e. 9unior developers can review senior developers etc

!ut all names on post-it notes and put on wall. 6et time someone

needs a review take first person at top of list and thats who reviews

your code

A$$ )*" C& @"LC">"

6o matter how small

(


20/26

"ample Cn this case send back right away and format the code properly

3:


21/26

Cf someone says formatting isnt important, show eample of plain tet writing using the

same formatting. Cts difficult to read.

3(


22/26


23/26

"ample of what a reviewer would return to the initial developer. )an be done in email

form 1keep this as simple as possible to start2.

38


24/26

Kou will face challenges, most of them cultural. &tick through it

35


25/26

Tools

)ode review tools are not required. Cf initially starting off 9ust use email.

4 oc for &'$ eveloper http%%www.that9effsmith.com%archive%3:(3%:8%9avadoc-for-

the-database-a-la-dbdoc-via-sql-developer%

3?


26/26

building a better team web

Documents