Sharing

Knowledge

Across

Team

Get back to non-Patrick people paying attention to the community

Let's look at 

tech Debt

Consider the API When planning

I wish our standups were faster

keep Rick's Teams in the loop

Paired programming

and 

paired testing 

ARE good

don't be "okay" with 

not finishing stories

Remember to task stories and to move stories on the board

Update Acceptance Criteria as User stories evolve

Don't make complex, questionable changes late in a release cylce

Think through wonky scenarios when updating UDF's

keep all active parties up to date on user stories

Keep an eye on our team efficiency as we grow

Update Dev Env Documentation 

as it evloves