The Agile Engineering initiative is now closed
Our purpose is to surface the techniques already emerging among engineers who work closely with software and give visibility to help spread these practices. The scope covers any kind of programmable technology – PLCs, FPGAs, ASICs, ladder logic, and firmware. We will do this by posting short descriptions of techniques that we receive from you. Anyone can play a role in the development of agile engineering practices by contributing an Agile Engineering tip.
These Agile Engineering Tips should be:
- Proven in practice
- The first-hand description of the Problem, Action, and Result you achieved
- Written assuming your reader is a peer
- Granularity sufficient for the reader to duplicate your experience
- About 1 or 2 pages in length
The process for getting your Agile Engineering tips published here is simple. Just tell us about it and we’ll communicate with you through email to resolve any questions – ours or yours – and that’s it.
This program is primarily for spreading proven techniques that help implement Agile principles in programmable hardware and firmware. A Tip can come from industry or academia but should be written by the person who actually implemented it. Tips will be reviewed for:
- being in scope (the charter of AA says it’s a software organization, so our scope is programmable technologies of all sorts. For the present time, other kinds of engineering are outside scope, but we’d like to hear from you if you want to discuss this.)
- being clear and detailed enough that a person of similar background could implement the tip. – length. Prefer 2 pages max but will consider some variation. If it’s very long, perhaps it should be 2 or more tips.
- not overly commercial. Please don’t send disguised advertisements for your product. It’s ok to mention specific tools and even vendors but we’ll use our judgment to keep the content to be relevant to practitioners, by screening out things that appear to be advertisements.
We encourage the use of visual elements – a photo of your lab set-up or a device layout diagram is good to have. Several images can be part of one tip.
Help spread the word!
- Invite your co-workers to submit tips
- Tweet about this program using #AgileEngineering
- (sharing buttons on the website for Facebook, Twitter, etc.)
- badge to put on your site or blog