September 7 Meeting
Free and Open to the Software Engineering & IT Community
Construx Software, 10900 NE 8th St Suite 1350, Bellevue, WA
Food & networking from 5:45 to 6:15 (pizza, salad, soda )
Announcements from 6:15 to 6:30
Presentation from 6:30 to 7:45
Q & A from 7:45 to 8:15
Doors close at 8:30
We start presentating earlier now to allow for questions within the 8:30pm meeting time.
Lightning Talks on Software Process & Quality
Presented by 8-10 of your fellow SEASPIN participants
The format is the "lightning talk" where each presenter has only five minutes to present their idea (one at a time). The topics include just about anything related to software quality or process in that time – a new idea, lesson, technique, or experience they want to share. Q&A will follow after.
Speakers so far... ( Topic details to be announced. Stay Tuned! )
Quallaboration
Jim Benson |
TBD
|
Self-Healing Systems or How I Finally Got My Roommates To Keep Our House Clean
Jeremy Lightsmith |
----
My 5 roommates and I have lived together for 4 1/2 years, and in that time we tried at least 6 different systems and sets of rules to get everyone to keep the house clean. Though some of them worked for a month or two, eventually all of them failed… miserably.
Eight months ago, we started keeping a new type of chore chart and we've had a clean house ever since. More importantly, we think we know why!
Our chore chart is a self healing system, and it shares characteristics with other self healing systems. It:
- uses simple rules
- expects & tolerates faults
- visualizes work
- encourages forgiveness
- discourages heroes
- is gameable
Perhaps the same traits that are keeping my house clean can ensure you deliver value to your customers. |
Visual Proof of Little's Law
Steven Borg |
----
Illustrating how reduced work-in-process drives faster cycle-time. In other words, how agile act ually makes sense. |
Toward More T and Less BS
Jon Bach |
----
Testing is like a bird looking for worms. You fly around and decide where to land (Setup activities), start covering the ground (Test Design and Execution activities) and then find a worm (Bug Investigation and Reporting activities). These three activities can be reported as S, T, B but also as a percentage of time spent on each activity during any given project, sprint, day, or test session. It’s perfectly scalable and provokes discussions. Since B and S time represent interruptions to T, I’ll show you some test reports that demonstrate the effectiveness of this simple reporting approach. |
Leverage in Design
Jeff Smith |
----
Process is just one of the productivity levers in the Software Engineering toolbox. Architecture and design remain a critical skill in maximizing productivity & perhaps creating new markets. |
Software Debt and Portfolio Management
Chris Sterling |
----
This 5-minute talk will discuss the ills of project portfolio management when quality is not understood and part of the strategic planning process. Are we XX% done? Can we deploy what we have to focus on other priorities? The lightning talk will take on 5 ills we should watch out for and early warning signs of their potential occurence. |
|
Leading Offshore Teams
Mira Latoszek
|
----
Quick points on:
- my experience with a remote, overseas test team in an agile environment
- tips for finding and selecting the right team
- setting up an effective communication processes
- overcoming cultural and language barriers
- pros/cons of testing with a 12 hour time difference |
Creating a Quality Index
Jim Hancock |
----
Most software development has become "agile," but CMM, CobiT, PMBOK, Malcolm Baldridge and other quality process metric deployments are still large and complicated. Jim will discuss how to deploy software quality metrics that meet the following criteria: objective, non-obtrusive, flexible, repeatable, consistent, holistic, efficient and inexpensive. Most importantly, the Quality Index will provide an accurate assessment of risk and quality within any SDLC upon which logical deployment decisions can be made. |
API Peer Reviews - how to improve your software interface in less than four hours
Bob Watson |
----
API peer reviews collect user feedback on an API before it's been released. In fact, you can get user feedback before you even begin coding!
An API peer review is a short, focused review session in which engineering peers review the use of an API as customers. This review method can be applied as early as the design phase of an API and provides a quick way to find design problems that could otherwise go unnoticed until after release. API peer reviews provide a rapid, low-cost alternative to laboratory-based API usability studies and compliment traditional design and code reviews. |
Still looking for more noteworthy speakers... Check out our group on LinkedIn.
View map by MapQuest
Going North on I-405 toward Bellevue...
- Take exit 13B for NE 8th Street
- Take the NE 8th Street West ramp
- Merge onto NE 8th Street
- Turn right onto 110th Avenue. Construx is the building on the left, on the corner of 110th Avenue and NE 8th Street
- Turn left into the parking lot immediately past the building
Going South on I-405 toward Bellevue...
- Take exit 13B for NE 8th Street
- Take the NE 8th Street West ramp
- Merge onto NE 8th Street
- Turn right onto 110th Avenue. Construx is the building on the left, on the corner of 110th Avenue and NE 8th Street
- Turn left into the parking lot immediately past the building