Serverless computing feels like it’s been a “hot trend” forever. Even before AWS Lambda first introduced the concept in 2014, it’s been hailed as both a saviour and a curse, finding its way onto countless lists of IT and software development trends. So, what’s the truth, where is it going, and why are we still talking about it? The reality
CTO seems like a natural career move for many senior technologists. However, it may not be for everyone, and it’s not always the most straightforward transition to pull off. So, what, really, is a CTO? And what makes them tick? And more importantly, what makes a good one? We were privileged to be joined recently by three inspirational CTOs, from
Some of the most successful CTO’s I’ve ever worked with come from non-technical backgrounds. At a time when technologists and businesses seem to worship technology, it’s important to take a step back and question if that’s really where technology leaders should be focusing their time and energy. I strongly believe that the future of technology leadership is much more about
101 Ways helps Abcam digitally transform to better empower life science researchers at a time when it is needed most Technology consultancy 101 Ways today announces that it is working with Abcam a global innovator in life science reagents and tools, to expand its digital services to the life science community. Aiming at developing and delivering a new digital operating
If the pandemic has taught companies anything it’s that tech is not something that you put off and think about ‘later’. The last year has seen organisations go through huge digital transformations, whether planned or otherwise. And for those that aren’t technology-based companies, getting the right board-level advice can not only be hard to find, but the difference between success
In my mind, active user involvement is the first of 10 key agile principles. It’s not always possible to have users directly involved in development projects, particularly if the agile development project is to build a product where the real end users will be external customers or consumers. In this event it is imperative to have a senior and experienced
An agile development team must include all the necessary team members to make decisions, and make them on a timely basis. Active user involvement is one of the key agile principles to enable this, so the user or user representative from the business must be closely involved on a daily basis. The project team must be empowered to make decisions
In agile development, requirements evolve, but timescales are fixed. This is in stark contrast to a traditional development project, where one of the earliest goals is to capture all known requirements and baseline the scope so that any other changes are subject to change control. Traditionally, users are educated that it’s much more expensive to change or add requirements during
Agile development teams capture requirements at a high level and on a piecemeal basis, just-in-time for each feature to be developed. Agile requirements are ideally visual and should be barely sufficient, i.e. the absolute minimum required to enable development and testing to proceed with reasonable efficiency. The rationale for this is to minimise the time spent on anything that doesn’t
How do you eat an elephant? One bite at a time! Likewise, agile development projects are delivered in small bite-sized pieces, delivering small, incremental *releases* and iterating. In more traditional software development projects, the (simplified) lifecycle is Analyse, Develop, Test – first gathering all known requirements for the whole product, then developing all elements of the software, then testing that
Agile development is all about frequent delivery of products. In a truly agile world, gone are the days of the 12 month project. In an agile world, a 3-6 month project is strategic! Nowhere is this more true than on the web. The web is a fast moving place. And with the luxury of centrally hosted solutions, there’s every opportunity
In agile development, “done” should really mean “DONE!”. Features developed within an iteration (Sprint in Scrum), should be 100% complete by the end of the Sprint. Too often in software development, “done” doesn’t really mean “DONE!”. It doesn’t mean tested. It doesn’t necessarily mean styled. And it certainly doesn’t usually mean accepted by the product owner. It just means developed.
Search the Blog
What am I interested in?
Agile Management Made Easy!
All About Agile
By Kelly Waters
“’Agile’ is one of the biggest buzzwords of the last decade. Agile methods often come across as rather more complicated than they really are. This book is an attempt to unravel that complexity. To simplify the concepts. This book breaks the concepts into small bite-sized pieces that are easy to understand and easy to implement and delivers the message in a friendly and conversational style. Allaboutagile.com is one of the most popular blogs about agile on the web. ”
Agile 101 is available to purchase. GAME ON!