The invisible cost of double jobbing for shared resources in Agile
The stated ‘best practise’ of Scrum-flavoured Agile software development (and therefore the target state of many transitioning environments) is a self-organising, cross-functional collection of individual resources capable of delivering whatever they agree to deliver, within a time window and within the resources (including
