Skip to main content

planetary system

Until 1781, humans had believed there to be only six planets (including Earth) in the solar system. Although many eminent astronomers had previously spotted the planet Uranus, they had always presumed it to be just another star and listed it as such.

In March 1781, William Herschel made a series of parallax observations through his telescope and believed he had discovered a comet. On 26th April that year, he reported his find. Only after feedback on his report from the Astronomer Royal and independent confirmation from European astronomers, did he finally concede he had discovered a new planet. After some discussion, Berlin astronomer, Johann Elert Bode, named the planet Uranus.

Herschel brought the number of planets in the solar system to seven. Later, Alex Bouvard noticed some unexpected perturbations in Uranus’s orbit and predicted the existence of yet another planet. Johann Galle visually confirmed Neptune’s presence in September 1846 and brought the number of planets to eight.

No, they didn’t! None of those people increased the number planets at all. They were simply the first people to see and catalogue the ‘new’ ones. For thousands, if not billions, of years, the number of planetary-sized rocks orbiting our sun has been eight. You might argue about the definition of ‘planetary-sized’ but according to the current definition, that number is eight, has always been eight, and is likely to remain eight until an astronomical catastrophe occurs.

Similarly, your project didn’t change from a six-month project into a three-year project. Herschel, et al didn’t launch new planets into space and nobody came along and invented new requirements for your project. All of these things existed from the beginning.

Your project is like astronomy. In its early days, none of the participants had the skills or technology to identify all of the planets. Sorry, I mean requirements. That doesn’t mean they weren’t there. It simply means you didn’t know about them.

Now, we have better knowledge and tools and we’ve used them to look at your project. We’ve discovered some stuff those early pioneers missed but thankfully, we’ve found it now.

Aside from the Geocentrics and possibly the Flat-Earth Society, I imagine most people of the eighteenth and nineteenth centuries welcomed the new knowledge that expanded the number of known planets. The discoverers of those planets reaped handsome rewards as heroes of science.

Compare this with the individuals that discover the hitherto unknown requirements in your project.

Will you treat them as the heroes they undoubtedly are and reward them for expanding your knowledge of the known requirements?

Popular posts from this blog

The Business Value of Telemetry

Dynamic technologies and infrastructure allow server failures and network issues to be quickly addressed, easily mitigated and, in many cases, reliably predicted. As a result, there’s a new venue opening for IT: end-user telemetry, which enables IT to determine how its internal users are consuming business resources, what type of application issues they are experiencing and how it impacts business performance. Gartner suggests that infrastructure and operations (I&O) leaders must change their approach and prioritize top-down business-oriented metrics. The research firm predicts that “60% of IT monitoring investments will include a focus on business-relevant metrics” by 2021, up from just 20% this year. Changing The Game Of course, it’s one thing to recognize the value of business-driven metrics and another to implement effective monitoring processes company-wide to overcome key barriers to effective digital transformation. The first step is understanding the fundamental shift requi

The Customer Paradox

We all have customers. Some of them are real live customers, people we deliver a tangible product to in return for financial reward and others are merely the next link in our production chain. Testers, for example, are customers to developers. The one thing all customers have in common is they are happiest when they are given exactly what they want. When I think back to the times I′ve been a customer, be it in a shop or maybe a restaurant, I remember how annoyed I was when given something I didn′t ask for and didn′t want. Even more annoying though, were the times when what I was given wasn′t what I wanted and it was what I asked for. This brings me to the customer paradox, which can be stated as, "the harder you try to define your customer′s requirements, the less likely you are to deliver what he wants." This is especially true about software development and, in my opinion, it′s largely to do with the way we approach project management. Yes, you′ve guessed it, I′m having a d

The Death Knoll for the Agile Trainer

The winds of change blow fiercely, propelled by AI-driven virtual trainers, and I can't imagine for a minute that certification organisations have not already recognised the potential for a revolution in training. They may even already be preparing to embrace technology to reshape the Agile learning experience. Traditional face-to-face training and training organisations are on the verge of becoming obsolete as virtual tutors take the lead in guiding aspiring Agile practitioners through immersive digital experiences. The future of training and coaching lies in AI-driven virtual trainers and coaches. Trainers, powered by artificial intelligence engines such as ChatGPT, are set to revolutionise the learning experience. With AI-powered virtual trainers, learners can engage in immersive virtual environments, actively participate in simulations, collaborate with virtual team members, and tackle real-world scenarios. These trainers automatically analyse progress, provide instant feedback