Advice from the
Read through our resource hub to find articles on a variety of topics including tips on successfully delivering software projects and blending business and IT, insight into the processes we follow for development, and even information about the technologies we use.
Budgets for agile software development initiatives can be hard to pin down. When starting a new software project, more is unknown than known, but having an accurate budget is very important for the business. This puts a lot of pressure on the Product Owner to get the budget right. No one wants to have to go back to their stakeholders and ask for more money later on.
We’ve all been there before. It’s late into a meeting and the product owner comes up with just one more nice-to-have feature to sneak into a work-in-progress. The youthful or inexperienced developer next to you pipes up, “Oh yeah, we can do that. I can have that knocked out in five minutes.” You rub your eyes and then let out a small sigh. You know it won’t take five minutes.
What is the mindset around development work at your organization? Do you approach work with a project or a product mentality? In development circles there is currently much conversation around shifting away from a project mentality to a product mindset.
As the Product Owner on a software team, your main role is often broken down into two parts: ownership and communicating what’s known as the 3 V’s–Vision, Value, and Validation. In this post, we’re going to focus on vision and the importance of clearly communicating vision for your software.
Long before the word COVID-19 was in the news, Aptera started hiring remote developers and implemented a remote-first mentality. Because of this change, our teams were uniquely qualified for the complete shift to remote work – including our in-office staff. While we’ve made the transition to remote work as seamless as possible, we understand this isn’t the case for every team.
With the onset of the novel Coronavirus, companies across the country and around the world are trying to navigate how to work remotely. Many developers are already accustomed to working remotely; Aptera has several full-time staff members who work from their homes. But if it’s new to you and your Scrum team, it can feel challenging to hold Scrum events and collaborate with your teammates across distances. To help, we’re sharing our top tips for collaborating and holding Scrum events when some or all of the team is remote.
When it comes to software development, there are many different procedures or value systems that can be followed or drawn upon for workflow. Two development philosophies that are often talked about and compared are agile and Waterfall. In a way, they are two sides of the same coin, Waterfall is slower and methodical while agile is faster-paced and nimble. Depending on your project and your organization there are pros and cons to each method. Choosing the one that best aligns with your company’s goals and work mentality will give you the best outcome and the smoothest development process.
The need for qualified software developers only continues to grow and companies looking to increase their development staff are finding that it’s a candidate-driven market. Today’s tech recruiters need to be more strategic than just matching backgrounds or tech stacks with a list of requirements. Essentially, you’ll need to become a sales person for your organization and pitch why your company is a good choice for your candidate. Having been navigating these hiring waters ourselves over the last few years, we’ve picked up a few tips for finding developers for your staff.
Sure, every first day on a new job starts with HR paperwork and an office tour, but to create a culture where developers specifically are set up to thrive, we recommend going a few steps beyond the basic onboarding. Within the first day or two on the job, after showing your new development hire where the coffee is, set them up for success with the points on this onboarding checklist.