I’ve got a vague idea as to what they get up to, mostly because I’m always bothering them to get updates on how my clients’ projects are going. And I know they are in constant contact with various development teams and review calls with clients all the time because it’s so damn hard to get some time with them!
However, I wanted to know more about their day-to-day tasks, and I thought it might be interesting for you.
I booked some time in to talk with Jaimit Modi, one of our Project managers. He was an android developer and naturally grew into managing dev teams as he’d seen so many projects from start to finish.
Ket: Hey Jaimit! Thanks for taking some time to out to chat with me, I just wanted to learn more about your role as a project manager at Satva Softech.
Jaimit: Hey Ket, pleasure!
Ket: Awesome! So, tell me, what does a typical day look like for you as a project manager at Satva Softech?
Jaimit: Well, you know, every day is a bit different in my role, but it usually starts with a cup of chai!
Ket: I mean for work!
Jaimit: Ha! I start with reviewing project progress and checking in with the team. We have a morning meeting where we discuss tasks, address challenges and answer any questions they may have. Throughout the day, I stay on top of project timelines and make sure everything is moving forward as planned. Communication is key for me, so I’m in touch with clients, developers, and other departments to keep everyone in the loop. Look at this – I’ve got Teams, Skype, WhatsApp, Trello, Azure and all these other tabs open to communicate with different teams!
Ket: Sounds pretty fast-paced! You mentioned discussing tasks with the teams, what are the key tasks and responsibilities that YOU handle?
Jaimit: Mine are mainly the tasks that revolve around planning the project like defining timelines and setting milestones. Then I organise myself to keep on top of them AND my project team routinely. I also take care of allocating the right team members, making sure the right developers are working on the right tasks, as most of my projects have a mixed tech stack, say android, iOS, .Net and so on. Risk management as well; I try to identify challenges early on, potential ones, and come up with strategies to tackle them, but don’t forget.
Ket: Sounds like there’s a lot on your plate, but it’s great to see that you’re managing everything! How do you contribute to the successful completion of software projects at Satva Softech?
Jaimit: Teamwork is everything to project success! I focus on fostering collaboration and open communication between everyone. I feel that if I can give my team crystal clear direction then motivating them and resolving issues that come up becomes collaborative, so we ensure that everyone is working together seamlessly towards achieving our project goals. Meeting client expectations and delivering a high-quality product on time and within budget are always high on the priority list too.
Ket: Teamwork makes the dreamwork!
Jaimit: Such a cheesefest!
Ket: During project planning for software projects, what activities do you typically undertake at Satva Softech?
Jaimit: In project planning, I work closely with everyone involved to define the project scope, goals, and deliverables. We estimate project timelines and allocate resources accordingly. Of course, risk assessment is a significant part of the planning phase; we want to identify any potential hurdles and be prepared for them. That way, we can ensure a smoother project execution.
Ket: That’s a great approach to leadership! Could you explain its importance at Satva Softech and how you handle it?
Jaimit: So… Risk management is crucial because it helps us identify potential challenges early on. By doing so, we can come up with strategies to address them proactively, reducing the chances of any unexpected issues derailing our project. It’s all about being prepared and staying ahead of the game.
Ket: And how do you monitor and keep control of software projects to ensure they stay on track and meet their objectives?
Jaimit: Regular monitoring is essential. We keep a close eye on project milestones and performance metrics, making sure everything is progressing as planned. If we encounter any deviations, we take swift action to get things back on track. Staying on top of project progress helps us ensure that we’re meeting our objectives and delivering the best possible outcome.
Ket: You mentioned earlier the importance of communication in project management. What communication strategies do you employ at Satva Softech to keep everyone involved informed and engaged?
Jaimit: It’s near enough the first thing I do – I arrange when and how often I’m going to catch up with clients. Most often we’ll pencil in a weekly or fortnightly call. The team and I already know that we’re going to have daily standups. These regular meetings keep everyone involved in the loop about project progress, challenges, and achievements. Status report updates as well but I don’t want to bore you with detail!
Ket: What about QA (quality assurance)? How do you ensure quality standards?
Jaimit: We all agree to and set quality standards that we adhere to throughout. These are based on the budgets and timelines that have been agreed with a client but regular reviews, testing, and feedback sessions are all part of our approach to maintaining the highest possible standards.
Ket: I won’t go into budgets vs expectations there’s enough content about that on the socials! How do you handle resource allocation and management in your software projects?
Jaimit: Yes, this is usually set early on but as you know things often change. It involves assigning the right team members with the appropriate skills to each task. However, there may be a new request from the client so we might need a particular developer with a particular skillset for longer than planned or we may need the designer to come back in to help solve an issue that comes up way after they’re out of the project.
Ket: And Budgets for the resources? Is that for you to think about or do you stick to what we’ve confirmed during the estimating stage?
Jaimit: It’s integral! Yes and no. You’ll set the budgets based on the client’s needs and I’ll track the project expenditures, I’ll often have to make some difficult decisions to stay within the allocated budget. Staying on budget ensures that we can deliver the project without any financial constraints.
Ket: Staying on budget is always important for the success of a project. Could you tell me about the documentation practices you follow during software projects at Satva Softech?
Jaimit: Documentation is a critical aspect of project management. We maintain comprehensive records of meetings, plans, and project-related documentation. This helps us keep track of project progress, decisions made, and outcomes achieved.
Ket: Now, let’s hear about challenges. How do you address challenges and implement change management strategies during software projects at Satva Softech?
Jaimit: Challenges are part and parcel of any project, but we tackle them head-on. We encourage open communication and brainstorm solutions together as a team. Implementing change management strategies involves evaluating change requests carefully and understanding their impact on the project. By making informed decisions, we ensure that any changes are smoothly integrated into the project without causing disruptions.
Ket: Proactive! How about after completing a project, are there any post-project evaluations you conduct to assess project success and gather lessons learned?
Jaimit: Yes, I’m big on continuous improvement. I conduct thorough assessments to evaluate the project’s success and gather feedback from everyone involved, I know you get involved too by asking the client what they thought of us. It good to identify what worked well and areas for improvement, helps us learn and apply these lessons next time around.
Ket: Tell me about these projects, I’d love to hear about some of your successes. Could you share any specific examples of projects you have managed at Satva?
Jaimit: I’ve been lucky, I’ve had the pleasure of working on some incredible projects here. One of the reasons I got into tech was because of the great impact it can have on improving our lives. And one project that stands out is the work we did with CCR and our client Ali. It involved developing a new mobile application to reduce the admin burden on his drivers. The drivers are tasked with home to school transport for kids with special educational needs.
I headed up a team of 8 developers popping in and out of the project at different stages and milestones. The biggest reason I loved it was the fantastic collaboration between the team and the client…so much so that he had me work out of his office 2 or 3 days a week. I had regular meetings and updates to keep everyone engaged and informed throughout.
By staying on top of project timelines, addressing challenges swiftly, and ensuring quality at every stage, we were able to deliver the product on time and exceed the client’s expectations. Since then, we’re probably on project number 5 as Ali’s always looking at new ways to improve the app and add value for his customers.
Ket: That sounds like a great success story! Congratulations on that accomplishment. It’s clear that you have a solid approach to project management at Satva Softech. I appreciate you sharing your insights and experiences with me today, Jaimit!
Jaimit: Thank you, Ket! It was a pleasure chatting with you and sharing my experiences. If you have any more questions or need further information, feel free to reach out anytime.
Ket: I definitely will! Thanks again, Jaimit. Have a great day!
Jaimit: You too, Ket! Take care!
Why Different Software Development Methods Affect CostsSoftware development doesn’t come cheap. But precisely what you’ll pay depends on various factors. There are obvious ones, like the number of features in your software and their complexity. And slightly less obvious ones, such as the experience and expertise of the software development team and where in the world it’s located. However, the final tab also depends on the software development company’s approach and techniques. This blog post will explain more about software development companies’ different approaches and techniques, the pros and cons of using them, and how they affect costs. Is Test-Driven Development always more expensive? If your software developer uses a Test-Driven Development (TDD) approach, your costs will likely be higher. In TDD, instead of launching straight into writing the code, developers create a ‘test case’ for every piece of code, no matter how small. This means they decide how each code should work before writing it and then check it against the test case. The TDD approach could stretch development time by at least a third, possibly two-thirds. So, a project that might otherwise take 6 weeks to complete might take 8 to 10 weeks and cost considerably more. However, although TDD requires more time and effort upfront, it usually results in higher-quality software with cleaner code, which could save you money in the long run. This is because every code is tested automatically during the development stages. In turn, this means that developers address any problems immediately, so you won’t have to pay to fix them later. Deciding whether or not to use TDD depends to a large extent on what you’re doing. Writing all the test cases might seem excessive for smaller and simpler projects. However, the approach can help produce reliable, top-notch software with low maintenance costs for more complex projects. Can different architectures influence cost? Over the years, development companies have used a range of architectures – or methodologies – to help manage the software development process. Over the years, better technology and servers have led to more sophisticated architectures. First, there was MVC, which stands for Model (the software data), View (what you see on the screen), and Controller (how the software responds to your actions). This enabled developers to work on different parts of code separately. MVC then evolved into MVVM, with ViewModel (VM) emphasising the interaction between the data and its appearance on the screen. This made it easier to develop more intricate user interfaces. Later came Microservices Architecture, which breaks complex software into individual components so developers can work on one piece at a time. How you build software can affect how long it takes to finish a project and how much it costs. While it’s vital to improve methodologies, it can be challenging. It involves learning new things and extra costs for implementation and training. Some companies embrace the change, completing projects faster with the more recent processes. In contrast, others stick to their old ways, which might take longer and be more costly. Different software development architectures can indeed influence project cost and duration. However, it can also significantly impact software development outcomes. How important are human resources? In software development, having the right individuals in the right roles plays a crucial part in producing a top-quality product on time and within budget. The importance of this is impossible to overstate. However, the dynamic nature of technology and the diversity of skills required means this is easier said than done. Identifying the ideal candidate for a specific job involves assessing their skills, experience, and adaptability – while also considering the evolving demands of the project. Team dynamics and the availability of suitable candidates make the job harder still. Consequently, achieving a precise fit between individuals and roles requires meticulous planning, ongoing evaluation, and adaptability. Achieving a perfect match between team members and their roles in software development is critical for project success. Do prototypes add to costs? In the case of some software projects, the development process starts with a brief that outlines the project requirements. The work is then divided into smaller phases called sprints, each with its own set of tasks and goals. At the end of each sprint, the development team reports on their progress, and the project manager provides feedback to guide the next sprint, ensuring the project stays on course. The other method is to design a clickable prototype of the finished project using a prototyping tool like Figma or Photoshop. The prototype will include a user journey, mapping out all the steps involved in using the final product. Once developed, the prototypes are presented to the stakeholders to show them how the final software will function. After gathering feedback from the stakeholders, the prototypes are adjusted before the development phase begins. While prototyping can help minimise errors and costly revisions, it does require an initial investment of effort and time which can add to costs. Weigh the benefits of reduced revisions against the upfront prototype development efforts. Is it cheaper to have a Continuous Integration and Continuous Delivery Pipeline? A Continuous Integration, Continuous Delivery (CI/CD) pipeline is a set of automated software development processes and tools to ensure that code changes are tested, integrated, and delivered smoothly and consistently. Implementing a CI/CD pipeline into software development projects can drastically reduce the time it takes to get products to market, significantly reducing costs. A CI/CD pipeline can also increase collaboration between the different teams involved in the project and make the whole development process more streamlined. However, building and managing a CI/CD pipeline takes time, and there are associated costs. Consider the long-term benefits against the upfront costs for your specific project needs. Documentation Software documentation plays a considerable but often overlooked part in the cost of software development. Keeping documents up to date is an important task, and you will usually need to pay an experienced and qualified person to do this on an ongoing basis. In a Nutshell Software development costs are
