Showing posts with label agile austin. Show all posts
Showing posts with label agile austin. Show all posts

Saturday, March 19, 2011

David Anderson in Austin - "Driving a Kaizen Culture Using Regular Operations Reviews"

David Anderson on March 17, 2011 spoke to a joint meeting of Austin SPIN, Lean Software Austin, IEEE CS Austin, and Agile Austin about a missing component of Kaizen culture, the Operations Review - what can your department do, how much of it did you do, and are you any good at it.
(I thought it appropriate since he espouses lean methodologies that he was wearing skinny jeans.)



Now this picture is not creepy because the girl in the cartoon is hugging David.

The Agile-Lean-CS-Spinners:

The main benefit of the standup meetings at a job was the after-meetings that allowed small teams of people, instant quality circles, to discuss and solve problems. This also struck me as a real benefit of this meeting - a chance to catch up with long-lost tech friends in the Austin community.

My random jottings:
Since academic software is seasonal, they share "Classes of Service" with car racing.
At the StandUp meeting only manage exceptions.
Many organizations only have a shallow implementation of Lean.
Real Kaizen is people just doing their jobs.

The meeting was a success - thanks to John Heintz for buying meals for everyone.

Wednesday, November 04, 2009

Agile Austin - Domain Driven Design and the Naked Objects Pattern


Last night at Agile Austin Eitan Suez explored the relationship of Domain Driven Design and the Naked Objects Architectural pattern to a packed house of 60 people.
The thing that struck me the most was how using the Naked Objects concept of having the objects themselves create the GUI forces a Ubiquitous Language on the developer since the user will see the object and method names on the screen.
Eitan gave a great example by having the jMatter framework autogenerates a permissions table with objects and their actions on the vertical axis and the types of users on the horizontal axis by reflecting the code and dynamically discovering the objects, their methods, and the types of users.