When developing a new product, system or service there are two primary ways you can end up going down the wrong path: (a) inadequate requirement capture means that you are developing something that may not work properly, (b) inadequate requirement validation means that you may be building something that nobody wants.
Verification and Validation – begin with the end in mind.
Developing any new product, service or system requires that it be both verified and validated. Providing the necessary assurance can require considerable time, effort and infrastructure to enact and it is important that this is considered from the outset.
New-look Website
Thanks to Bianca and her team at Magicdust for helping us to create this new-look website for Sigma Rose.
the Internet of Things – early days but picking up speed…
Recently, I was fortunate enough to attend the first meeting of IoT Sydney where we enjoyed a couple of excellent presentations and plenty of enriching conversation in the breaks. However, the main take-away for me was how far we still have to go in terms of interoperability, safety assurance and contextual awareness.
the Agile Trap
A key element missing from some of the popular support tools for Agile software development (eg Jira/Greenhopper, Rally, Basecamp et al) is dependency management. This, coupled with an approach to architecture that is often seen as an emergent element, creates a trap for those that might try to adopt Agile ‘Project Management’ without considering the higher levels of abstraction.
the Next 30 years
I attended the thought-provoking Warren Centre Vision30 lectures last week. We spent the whole day considering what the key drivers would be for innovation over the next 30 years. So, I thought I’d share some of the key themes with you…