The heart of agile software development is feedback loops. Doing a bit of software, looking at it, at how we did it and then improving things as we do another bit of software. The “things” that can be improved can be quality, scope, usability, performance etc. etc. Perhaps most importantly, relationships and ways of working…
Having a common understood architecture, regardless of the format of that understanding (documents, models, sketches, whiteboards, implicit team knowledge), is described as “Intentional Architecture”. Holistic Software Engineering described “good” architecture and design as having the following characteristics: Intentional structure and behaviour Highly modular: consisting of separate services, components, classes, objects or modules Elements are highly cohesive Elements…
Architecture is a high level view of a system in the context of its environment, dependencies, technology, structure and behavior. Architecture must be solid, useful and beautiful. Software architecture is typically hard to define as the term software architecture is used to describe many facets of software structure, behaviour, design, activity and documentation. The concept…
It’s pretty pointless building things that your customer doesn’t need or want. The first steps necessary in understanding how to deliver value to the customer: 1. Identify the value. – This must be done from the customer’s perspective. 2. Identify how that value is actually created. Lean thinking describes this as identifying and mapping the value stream – the activities that are…
An embarrassment of Project Managers An impasse of Architects A confusion of Business Analysts A mob of Developers A silo of Testers A brethren of Scrum Coaches A waste of Lean Consultants A conspiracy of Process Improvement Consultants People are important, not roles! But recently I saw a weekly team meeting for a project that…
We’ve released an update for Holistic Software Engineering (www.holistic-software.com) which: deprecates use-case diagrams in favour of scope diagrams emphasizes Integration Scenarios instead of “Scoping Use Cases” for Programme Backlogs updated versions of the Big Picture, Small Picture and COTS Implementation variants
Many teams I’ve worked with struggle to make sense of their huge backlogs of stories, struggle to explain the scope of a release and current work – and most importantly, struggle to explain how the stories they’re working on contribute to business value! All of these problems are killers when it comes to joining up…
HSD stands for Holistic Software Development which is a process framework that extends the principles of agile philosophy throughout the entire software development enterprise. Similar to “agile at scale” ideas HSD goes a few steps further integrating software development concerns from business strategy to continuous development, structural organisation to governance on the H-Model of software…
A quick introduction to Holistic Software Development (HSD). Holistic Software Development is a free process framework that combines agile, agile at scale, lean as well as portfolio, programme and project management into a single cohesive model.
I normally avoid posting on controversial things but this is a topic that shouldn’t even be controversial. The world is full of a marvellous variety of people and they come in all shapes and sizes, with a staggering range of ways of thinking. People are different due to things like gender, race, ability, sexual orientation,…