It’s that time of year when you mow the yard a little tighter on Wednesday so that come Saturday you can fire up the grill, plop yourself in the La-z-Boy®, grab the clicker, and watch your favorite football team. As with the rest of life, technology has been increasingly entering the football world. Whether it’s the use of ear pieces in helmets, better surfaces to play on, or lighter weight equipment to increase player speed, everything seems to be getting an upgrade. IoT is getting in on the action as companies race to find ways to improve sports performance. What follows is a list of three of the most interesting areas where devices are being developed for football.
What we have to say, what you want us to hear.
That’s how our blog works. It’s interactive. Let’s learn together.
Welcome back to the Meet Our Team Q&A series. My name is Daniela Williams, Project Manager at ISE, and I’ll be asking ISE team members questions to help give insight into what makes us tick.
Today I'm interviewing Tony Bopp, Quality Assurance Engineer, lead of the Philanthropy Committee, and ISE’s resident photographer! Read on to learn about how ISE helps out around the community and ideas to foster philanthropy with other companies.
Are our retrospectives valuable? Are our teams improving? These are two questions that come to mind when I think about comments or articles I've seen about resistance to retrospectives or the time spent in them. I think we can learn a lot by conducting a retrospective… on our retrospectives. Through such a retrospective we seek learning by exploring the following questions:
The Hardest Part of Software Project Management
I have been a software engineer and project manager for over 20 years. Can you guess what I’ve found to be the hardest part of managing software engineer projects? It isn’t persuading the engineers to put aside their running shoes and holey T-shirts for customer visits. It’s not riot prevention when the coffee pot breaks down. It’s figuring out how much it’s going to cost to build the software and then persuading the customer that that’s really how much it costs to build the software. As a rule of thumb, if the price feels right the first time you hear it, it’s too low.