Join thousands of book lovers
Sign up to our newsletter and receive discounts and inspiration for your next reading experience.
By signing up, you agree to our Privacy Policy.You can, at any time, unsubscribe from our newsletters.
In the digital world, the business is technology, and technology is the business. Agile software development was the first wave of process change for digital business. Now it is time to update management models and thinking. Continuous Digital sets out a new management model for digital business. A management model that takes Agile to the next level. Allan Kelly describes how software is omnipresent in digital business, how software is an asset and needs treating as such. He describes new management paradigms for the digital and agile age: - How dis-economies of scale not economies of scale rule software development - When planning delays action - How value changes over time - The lifecycle of stable value-seeking teams - Budget alternatives for funding software development Digitisation forces companies to rethink the way they organize themselves. This book offers a template for new businesses and new thinking on managing that work.
Projects fail. Some say 40%% of all IT projects fail, some say 70%%. And it has been that way for years. Each project fails for its own reasons but they all share one thing in common: the Project Model. Could it be the project model itself which creates failure? In this tour de force Allan Kelly explains why the project model is a poor fit for managing software development. Working from industry recognized definitions of projects he describes how the model deviates from reality then goes on to discuss: - Why focusing on time, scope, and cost damages software, creates goal displacement and reduces quality. - How projects miss the bigger picture. - Why maximizing value demands work across projects. - When debt is good and how projects increase technical debt to the detriment of value delivery. Projects end. Successful software continues. Twenty-first century digital businesses want to continue and grow.
"How do I make my user stories smaller?" "What is the right size for a user story?" "What is the difference between an Epic and a Story? And where do Tasks and Sub-tasks fit in?" "Who writes user stories?" "Why user stories?" ""Do I have to use User Stories?"" Allan Kelly found himself answering these questions, and similar ones, again and again so... ""As a ... I want ... So that ... "" - this humble little who-what-why template has become the most widely used means of communicating requirements for Agile teams. In this slim volume Allan Kelly provides practical advice on writing, reading and working with user stories.
Sign up to our newsletter and receive discounts and inspiration for your next reading experience.
By signing up, you agree to our Privacy Policy.