What’s new in 2019? At first glance it might not seem terribly exciting: this year will see (much) smarter devices, faster wireless speeds and a wider acceptance of tools like blockchain — all technology you’ve read about before. But look a little closer at this year’s trends and you’ll see real progress.
Insurance isn't a physical thing. It’s a promise, a shared understanding, that an insurance company will be there for its customers when they need it — during an illness, after an accident or after some other trauma. Because of this, insurance isn’t a product most people like to think about when everything is going well. If you’re investing in new technologies, this may seem like a problem. How can you get customers who aren’t thinking of insurance right now to use your new technologies? Why build a new application if your customers aren’t going to use it most of the time?
Your company is about to begin a Big Data project and it seems overwhelming. That’s understandable — Big Data is, after all, big. There’s a lot of it, often generated by many different sources: Internet of Things (IoT) sensors, spreadsheet data or customer behavior online. And those are just a few examples of possible sources. As intimidating as Big Data can be, data management shouldn’t be painful, as long as you plan ahead. To make the most of the data you have coming in, your organization will need to build a Big Data management strategy — a plan for how you will manage, use, share and store data within your company.
After a custom application development project wraps up, it's helpful for everyone involved to come together, talk about the project and find closure. This meeting is called the Retrospective, and it is critical for a team, so they can learn from their mistakes and improve. Often, retrospection is a celebration — software development is difficult, complex and a completed project is an accomplishment. You’ll high-five your team, talk about what made this project successful and modify your process so that you can repeat your successes next time.
Your company has a big project coming up: a mission-critical application your company wants to launch three months from now. It’s your job to decide who is going to build the software. You’ve got a lot of choices: there are a range of technology consulting companies who submit proposals to you for the project, from offshore companies to brand new consulting groups to local established technology consultants. It’s a tough decision but because your leadership has made it clear that having the project done on or under budget is very important. Therefore, you offer the contract to the technology consulting company with the least expensive proposal.
At first glance, recruiting and talent acquisition might seem like the same thing — both involve finding technology consultants and IT talent and placing those consultants in open positions. That, however, is where the similarities end. What’s the difference? Here are two quick definitions:
When you’re going into a software development project, you usually have two choices when it comes to managing the project. You can choose to manage the project using a traditional methodology like Waterfall, or you can choose to use Agile methodology.
If you're invested in Microsoft technologies, migrating to the cloud, using the Internet of Things (IoT) or considering a move to DevOps, you need to be aware of Azure. You’ve probably heard of Azure — especially if you're familiar with the concept infrastructure as code — but you may not be clear on its finer points. So, what is Azure? Simply put, Azure is Microsoft's public cloud service. Like its competitors, Amazon Web Services (AWS) and Google Cloud, Azure offers infrastructure-as-a-service (IaaS) but also storage, databases, active directory and a host of other services.
Your company is running a major application that’s central to your business and it’s time for an update. It’s a small change — just one piece of the app needs a refresh — but everyone is dreading it. Why? The software was built as one big application, changing one piece of the code may mean that other code will break. It’s like playing dominos — each fix means something else could break. It should be a simple update but everyone involved knows that it’s probably going to be a project.