In my last post, I described the initial phase of determining the trajectory for a greenfield softtware project. Once you have established your vision and created a roadmap, the next step is to decide how the software system is to be built. This involves finding a suitable architecture for the system and devising a macroscopic design of the different components and interactions involved.
If you’re a technical leader overseeing the development of a greenfield software project, then you know how crucial it is to get the design right.
In this article and the next, we’ll explore how to approach the initial technical modeling of the system. We’ll look at some of the best practices for making critical decisions to establish an efficient development plan that will lead to maximum system quality and reliability. We’ll cover concepts such as the high-level characteristics of a system, user story maps, and what product roadmaps should look like.
Business startups face many different and complex challenges, and all of them threaten to slow down or break momentum during the challenging initial stages of business development. Luckily there are a variety of approaches, techniques, and tools available in 2023 to help you get started, bust through barriers, and break stalemates. From using services provided by others to adopting process changes that build good habits from within, here are the four biggest blockage-breakers we have used at Opreto in 2022 to keep our business moving forward.
As a technical leader, you must make software development decisions that minimize risk for your company, and doing nothing may seem like the safest path. However, sometimes the risk of doing nothing can be the most significant. So, how do you know when to take a leap and go for it and when to hold steady?
You’ll often hear about the importance of getting started, breaking ground, getting moving on a thing. Whether you have a specific goal you want to achieve, or you just want to get your feet in the door of a particular industry or technological stack, the outlook from a thousand feet can be daunting. So how do you choose where to begin?
How do you help someone solve a problem if you don’t speak the same language? You learn their language and teach them a bit of yours. Without a shared language, you won’t understand the problem, and your solution may not end up being a fit. You are endangering the entire project. Read on to find out how I establish a shared language with new clients.
When you begin something, it is important to define your mission. It is difficult to get a team moving in a single direction without one, and it is impossible to know whether you are succeeding or not without some idea of where you were supposed to be headed. Missions galvanize teams, and give structure to effort. As prosiglieres, we summarize our approach with the motto: “Clear Eyes, Steady Hands, Right Advice”. However there is more to be said about just what our objectives are, and what it means to pursue these qualities. Read this post to find out what our mission is - for ourselves, our teams, and for this website.
Names are important, but it is also possible to get hung up on one too much. It’s important to remember that the perfect is the enemy of the good. Trying to appeal to every audience - to cater to every taste, or account for every way your name can be twisted, is a foolish way to spend your first days in any kind of startup situation, whether you are part of a business, a non-profit, a community organization, or a band you started in your garage.
You’ve come up with a goal, broken it down into achievable tasks, input everything into your project management tool… and then spent the next four weeks rescheduling the first task. You know exactly what needs to be done but, for some reason, you can’t seem to get started. Sound familiar?