Snogblog Informal Musings on Formal Things



FFK10 Speaker

So, with everything that has been happening in the first part of the year, I have been neglect in announcing that I will be speaking at FFK10 (April 14th and 15th) in Koln, Germany! This is the German Flash User Group's annual to-do, with a great range of speakers like Seb Lee-Desisle, Ralph Hauwert, Jesse Freeman, Mark Doherty, and more! I'll be presenting "DIY Workflow, or, How Being Agile Can Break Your Back". It's a quick overview of popular workflows in our industry, what makes them successful, what makes them fail, and how to take parts from each that apply to your work and build your own workflow. It's a bit of a strange topic for a Flash conference, but I think we need to talk more about productive ways of teams working together, organically, than the usual "he said, she said" that comes with multidisciplinary teams.

I hope to see you all there! Tickets are selling out fast!



NASA Systems Engineering Handbook

Yes, I will concede it's not the first title that comes to mind when you start putting together that Easter reading list, but I stumbled across it yesterday and flipped through it to see what it had to offer. For the most part, I doubt I will ever work on a project of such scale that spans years, if not decades, and depends upon such meticulous planning.

However, there was one section that jumped out at me, and I felt would be of value to anyone dealing with technical projects. Buried among the 20-odd appendices, lies this little gem: "Appendix C: How to Write a Good Requirement". In this appendix, you are taught what a requirement is, how it should be worded, all of the elements to think about when crafting a requirement. The best part, is that it is in checklist form, and is only two pages long. This makes it VERY easy to integrate into any existing workflow without feeling like you are making a massive overhaul in your process.

Check out the appendix here: Appendix C: How to Write a Good Requirement

And the whole book can be found here: NASA Systems Engineering Handbook

I'm sure there are other bits of value in there, but if you read it for nothing else, read it for Appendix C!