When you're trying to put together a development team, you want to structure that team for success. It would be great to have all the perfect team members, but that dream cannot always be realized.
Every once in a while, a CEO will come up to me and say, “Our commercial software development is failing. I suspect my CTO is the problem.”
Those are some pretty strong words.
Choosing a mobile app development team is a big decision for your company.
A good decision can lead to the results you want: finished apps and features in an efficient, timely manner.
You have a clear vision for your company to push it even further ahead of your competition. And you’ve just had an incredible idea for a new mobile app (or a new feature) – to bring you closer to making that vision real.
Last week on TheAtlantic.com, Ian Bogost published an article titled Programmers: Stop Calling Yourselves Engineers.
In his article Mr. Bogost argues that those who are writing software applications shouldn’t claim to be “engineers” because they haven’t passed a state-mandated certification exam.
He says that the title "engineer" is "cheapened by the tech industry."
Although I wholeheartedly disagree with this premise, reading the article made one thing abundantly clear to me: those of us who create software for a living have a credibility problem.
You put down your coffee cup and smile to yourself. One thought keeps going through your head: "I am freakin' brilliant!"
You pick up the napkin--on which you've just sketched out a revolutionary idea for a new app--and walk out of Starbucks with a pep in your step. You need to get back to your office to start planning how to spend your millions.
Then it hits you.
"I have no idea how to build a software product."
"Another change?" I asked. My business partner looked up at me and replied with one word: "Yep."
It was 20 years ago, I was fresh out of UNH engineering school and six months into my third startup since high school. Our software company was just getting going and I had spent the last two weeks creating a detailed project plan for some new features. But we had just heard back from our first potential customers, and they had different ideas of what we should build.
I was having lunch last week with a friend, and we were talking about our respective professional services companies. As we were finishing he asked, "So, what's your capacity these days? How many projects do you think you can take on?"
I replied, "Virtually unlimited."
He looked up and gave me a hard look, his fork hovering over his plate. Then he smiled and said, "Yeah, right," and went back to eating.
He didn't realize that we've spent the last two years perfecting our processes so we can now spin up a new agile software development team in about two weeks.
In this blog post I'll share with you six secrets you can use to quickly ramp up more software development bandwidth when you need it.