For information about the next session, see Next Session.
Presentation materials from past sessions are maintained whenever they can be obtained. They serve as a useful reference base. This information can be found at Past Sessions.
Do you have something to contribute to a members session as a presenter? If so we would love to hear from you at firstname.lastname@example.org.
For potential presenters we have prepared some information for you in the form of Guidelines for Member sessions presenters.
Tuesday 4th May 2015, 5:15pm for a 5:30pm start, finishing around 6:30pm
at Fronde on the Wellington waterfront
You're welcome to invite colleagues and others, but please RSVP to email@example.com so we can ensure an appropriately-sized room.
The tension between software architecture and agility is not well understood by agile practitioners. If an agile software team spends too little time designing architecture up-front then they face increased risk and higher chance of failure; too much time and the delivery of value to the customer is delayed, and responding to change can become extremely difficult.
In this session Michael Waterman presents the six forces that affect context, and five strategies that teams can use to determine how much effort to put into up-front design – based on the findings of his PhD research into architecture design in agile development. These findings, which he calls ‘a theory of agile architecture,’ describe how agile software teams answer the question of how much up-front architecture design effort is enough.
Dr Michael Waterman is an ICT professional with more than twenty years’ experience, including 17 years as a strategy consultant to the telecommunications industry, designing telecommunications networks at the architecture level. He has recently broadened his experience with a PhD in software engineering. His research investigated the balance between software architecture planning and agile software development and has been well received by both industry and academia. Michael is currently working with Specialised Architecture Services (SpecArc), a recently-formed Wellington-based company created to deliver quality IT architecture services and solutions.
There is no charge to attend but please RSVP to firstname.lastname@example.org. You're welcome to spread the word and bring others too.
If you would like to receive these notices by email - send an email request to email@example.com
Material from past members' sessions is available on this site as a useful reference.
The purpose of these guidelines is to assist speakers and Software Quality NZ to jointly achieve a successful outcome at SQNZ Members' Sessions.
The objective of a Members' Session is to provide the audience with information they would find useful and can apply in their day-to-day work.
The audience comprises mostly senior IT
professionals familiar with Software Quality concepts and
terminology. There may be some students present but presentations should usually be aimed at experienced professionals. Typical attendance levels are 10 to 40.
Each Members' Session is organised by one committee member, who will be your primary contact for any matters relating to the meeting.
If you need to communicate with the SQNZ and have been unable to contact the organising committee member, then please email firstname.lastname@example.org.
Members session's are usually conducted as either workshops or presentations, we usually focus on one topic per session, with one or two speakers being the norm but sometimes more. Our organiser will be happy to discuss with you the desirable timings for the presentation or workshop and questions.
It is desirable, based on past member's sessions feedback, that a presentation include use of Powerpoint slides. We also encourage potential presenters to have accompanying notes and handouts available - thirty copies is the optimum number based on past attendances.
Software Quality NZ web site
SQNZ would also like to make the slides and other material available for download from this website. Your presentation will be posted at the top of our Past Sessions page from the week after the date of your presentation. In this way, we are building up a repository of material that will be useful to the software development community.
All presentation material is posted acknowledging the presenter.
Other format points
- Member's sessions times: 4:00pm to 6:30pm on the third
Thursday of each even numbered month
- We can supply a datashow (contact the organiser and let them know if you need one)
We are happy to provide assistance as required in preparation of the presentation. We can help in setting up Powerpoint or Word material and can assist with checking materials prior to the presentation.
A flier will be prepared about 4 weeks before the meeting date for distribution to those on our mailing list. You will be requested to provide a short description about the topic, your title/position and any other relevant information which will attract people to the presentation.
When you make your presentation or submit material to the SQNZ, you warrant that you are either the sole owner of the material or have full power and authority to publish it; you also warrant that it does not infringe any copyright or contain libellous or unlawful matter.
Copyright for material published and/or distributed by the SQNZ remains with the presenter.
The SQNZ is an independent body and provides information of a general nature that does not endorse or support any particular product or service.
Presenters are asked not to include industrial strength endorsement or recommendation of products and services in their presentations. Detracting from your competitors products and service offerings is also a definite no-no. We do not mind the odd logo or contact details creeping in on presentation materials so long as it is done tastefully. The distribution of business cards or contact details to attendees is quite acceptable as is promoting your material's presence on our web page starting from around the first of the following month for a minimum of three months.