Since Agile, comprehensive documentation are dropped, what about abstract documents, how to create them, where to capture all the valuable discoveries of the multi-disciplinary team, what to leave behind when
Since Agile, comprehensive documentation are dropped, what about abstract documents, how to create them, where to capture all the valuable discoveries of the multi-disciplinary team, what to leave behind when product is developed & delivered,
How to start with a minimal text of a user story, and then how to capture all the achievements in a minimal and crisp language such that along with the working software, there are also a un-ambiguous ubiquitous language emerges that concise component documents and Topic based texts are developed in that language,
I started my career in mid 90s with ERP implementation, Oracle eBusiness Suite;
those who remember at the time folks were divided into two tribes TECHNICAL and FUNCTIONAL each blaming the other side when things did not work;
and I was unfortunate enough to do both tasks and act as the liaison between them, being yelled at from both sides.
As a techie, I did performance tuning, a carrier that is now disappearing as cloud computing has made scalability unrecognizable from the past, with abundant of recourses ready to deploy from a pool.
In those days we had to make the best use of OUR limited physical resources, like kids when I was growing up we had to keep our FEW toys in good order, FINE TUNED and repaired them when needed.
In the last 15 years in ONTARIO Public Service I have been Sr. I&IT Architect and business analyst wearing the hat of Product Manager in Agile engagements!
(Thursday) 7:00 pm - 7:30 pm