Read on Twitter
There is no such thing as an IT project.
There are, however, projects that impact or are enabled by technology and information.
But "the tech" isn't the outcome; its a means.
There are, however, projects that impact or are enabled by technology and information.
But "the tech" isn't the outcome; its a means.
I remember once having a discussion with a colleague "Oh, but this is a tech upgrade; the business don't care about it. It really is an IT-only project"
"Hmmm... try scheduling that downtime & the business testing around financial year end. Think they'll care quite a lot..."
"Hmmm... try scheduling that downtime & the business testing around financial year end. Think they'll care quite a lot..."
Now, some orgs *do* have "IT projects" due to the structure. Which I've always found strange.
Usually then somebody's made an arbitrary decision over a tech solution, IT implement exactly what was asked for & the business get annoyed because it wasn't what they imagined.
Usually then somebody's made an arbitrary decision over a tech solution, IT implement exactly what was asked for & the business get annoyed because it wasn't what they imagined.
... hence the problem. Run a "project" in isolation & you'll get exactly what you ask for... irrespective of whether it's what's needed/imagined.
And BTW -- this whole "business" and "IT" divide. Really? In 2021?
Neither can survive without the other.
Neither can survive without the other.
