The Architect´s Napkin

Software Architecture on the Back of a Napkin
posts - 69 , comments - 229 , trackbacks - 0

My Links



Post Categories


Software development must deliver on budget - always
Yes, I mean it: we always need to meet the budget (be that time, money or whatever resource).1 This most likely is not your software development reality. So how come I´m demanding something so seemingly unrealistic, even preposterous? Why? The reason for the obligation to deliver on budget is simple: trust. Software development is a social endeavor. It takes not only two to tango, but also at least two to develop and deliver software: a customer and a software developer. To accomplish something in ......

Posted On Monday, October 27, 2014 11:27 PM | Comments (2) | Filed Under [ Spinning ]

Spinning – A Core Practice for Agile Teams
I´ve seen many teams struggling with agility. Faithfully they were trying to live by Scrum or Kanban rules – but still it was hard to “get into the flow”. Day to day business seemed to interfere with the ideal of the process definition. That made me think. What was missing? I´m a firm believer in the agile tenets of delivering incrementally, staying in close contact with the stakeholders for early/frequent feedback, and constant learning. So my guess is, if agility isn´t working yet, we need to try ......

Posted On Wednesday, September 11, 2013 8:40 AM | Comments (0) | Filed Under [ Spinning ]

Get into the flow with Spinning
Spinning as described in my previous article is all about flow. Its premise is: flow can emerge when work is partitioned in small, evenly sized chunks processed in a smooth manner. There is a constant input of requests to the development team. A backlog is filled with strategically important requirements, support is reporting bugs, feedback requires changes, management wants to see ideas realized on short notice. Under these circumstances any plan becomes obsolete within a day or two. Or a lot of ......

Posted On Friday, December 23, 2011 1:55 PM | Comments (6) | Filed Under [ Thinking outside of the box Spinning ]

Spinning – Getting Agile at the Core
Agility needs to get onto the next level – that´s what I tried to explain in my previous articles. After a reality check – what´s missing from Agile practice? –, and some general musings about how a next level of Agility could look like, here now some very tangible suggestions. Crank up the frequency Current Agile practice is suffering from too little attention to Acceptance. To change this, very, very clear Acceptance dates need to be set. Acceptance can only get into a real pulling mode, if dates ......

Posted On Thursday, December 22, 2011 10:49 AM | Comments (2) | Filed Under [ Thinking outside of the box Spinning ]

From Agile to Elastic
In my previous article I came to a couple of conclusions based on the reality of software development, or should I say “the nature of software development”? Here are the – to me - undeniable facts of what our industry is all about: Customers hardly know, what they want. Any specification is inherently fuzzy and incomplete. What fits the customer´s needs can only be determined by actually trying it out. The customer can only recognize a running piece of software as acceptable. Because customers hardly ......

Posted On Friday, December 16, 2011 2:19 PM | Comments (2) | Filed Under [ Thinking outside of the box Spinning ]

Agile Process Reality Check
Let´s get real about software development: It´s never going to be a quietly flowing river. Never. And that´s why the current approaches to software development like XP, Scrum, and Kanban will always cause pain. Their basic assumption is you should be able to isolate a team for a while to work on features. Leave it alone during an iteration or a sprint to complete a set of features, or at least sit still until the current feature is done. Certainly that´s what we all want as developers: being able ......

Posted On Wednesday, December 14, 2011 2:22 PM | Comments (13) | Filed Under [ Thinking outside of the box Spinning ]

Powered by: