“The documentation is super intuitive, we do not need code examples for our api.”
Haha!
For all my business analyst, product owners, quality analysts and developers out there…
recovering economist
“The documentation is super intuitive, we do not need code examples for our api.”
Haha!
For all my business analyst, product owners, quality analysts and developers out there…
Ok, so a work related post here – these are the 12 principles of Agile software methodology that I learned in training today.
We have followed this loosely in the past but are now committed to a more formal adherence.
So here we go:
#1.
Satisfying the customer is the end goal
#2.
Welcome changing requirements
#3.
Deliver software frequently
#4.
Work together daily (communicate!)
#5.
Build projects around motivated people
#6.
Face-to-face communication is preferred
#7.
Progress is measured by working (functional) software
#8.
The pace of development is sustainable
#9.
Technical excellence and good design enhances agility
#10.
Maximize simplicity (minimum viable)
#11.
The best software comes from self organizing teams
#12.
Team’s frequently adjust behavior towards improvement
For more on the tech world, I enjoyed Lost And Founder (Amazon), By:Rand Fishkin.