Gerard Forbes’ Post

𝐒𝐨𝐟𝐭𝐰𝐚𝐫𝐞 𝐓𝐫𝐚𝐧𝐬𝐟𝐨𝐫𝐦𝐚𝐭𝐢𝐨𝐧 Projects face numerous challenges, such as dealing with legacy systems that are difficult to adapt or scale, misaligned teams that work in silos without cohesive goals, and the accumulation of technical debt from years of quick fixes and outdated technology choices. Managing the complexity of transformations, specially large-scale software, requires both organizational and architectural transformation. Organizational structures help teams work together by making sure everyone is clear on their roles, and how things should get done, making collaboration between departments easier. 𝐓𝐞𝐚𝐦 𝐓𝐨𝐩𝐨𝐥𝐨𝐠𝐢𝐞𝐬 is about organizing teams in a way that improves workflow, minimizes mental strain, and encourages clear communication. It defines different types of teams and how they interact to help deliver value more efficiently. Combining 𝐃𝐨𝐦𝐚𝐢𝐧-𝐃𝐫𝐢𝐯𝐞𝐧 𝐃𝐞𝐬𝐢𝐠𝐧 and 𝐓𝐞𝐚𝐦 𝐓𝐨𝐩𝐨𝐥𝐨𝐠𝐢𝐞𝐬 is important for successful software projects because it brings together both technical and organizational approaches. 👉 𝑯𝒆𝒓𝒆 𝒊𝒔 𝒄𝒐𝒎𝒑𝒍𝒆𝒕𝒆 𝒂𝒓𝒕𝒊𝒄𝒍𝒆: https://lnkd.in/d5zHaCpv 💡 This article is heavily inspired by the works of Matthew Skelton and Manuel Pais (Team Topologies) 🇺🇦 🇵🇸 , Team Topologies . Their book have been invaluable resources in shaping the content and insights shared. #DDD #DomainDrivenDesign #TeamToplogies

Transparent work processes help uncover inefficiencies and optimize workflows. Continuous improvement becomes easier when we can see where we can refine and streamline. https://buff.ly/3Vnw4QW #SoftwareDevelopment #MakeYourWorkVisible

Several historical sources accurately document the impact of centuries of rigorous documentation—thanks to documentation, entire disciplines evolved and changed for the better. Why is it so hard for companies to document their success? We favour speed, agility, and failing fast. The new mantra has driven an entire generation out of the well-defined and thought-through content that helps companies speed up their internal communication, accelerate the speed of discovery, design, and delivery, and adapt to change. So why don't we do it? ↘︎ Peers pressure ↘︎ Time pressure ↘︎ Clarity ↘︎ Reusability ↘︎ Agility (only the code matter) What will happen if you do; ↘︎ Find information 23% faster ↘︎ Have your own repository ↘︎ Build your IP if you are in that type of thing ↘︎ Define yourself as thought leader ↘︎ Deliver greater impact on the team ↘︎ Smarter delivery through shared knowledgebase. Do you want to know more Book On Us free discovery Call at: https://cal.com/givetm Reference: https://givetm.co/

Effective #ResourceManagement is essential to a well-run #ProductDevelopment team. Here are 4 warning signs it's time for a more strategic solution within your #ProjectManagement tools. Full blog post ➡️https://lnkd.in/g3wpTTha

“A complex system that works is invariably found to have evolved from a simple system that worked. A complex system designed from scratch never works and cannot be patched up to make it work. You have to start over with a working simple system." Gall's Law is a principle that the wonderful R. Colin Kennedy introduced me to recently. Derived from the book "Systemantics: How Systems Really Work and How They Fail,” John Gall points out that when complex system is designed from the ground up, it is likely to fail because it lacks the iterative refinement that comes from practical use and incremental improvements. So what if you already have a complex system and you want to make it simple? You might have to burn it all to the ground and start over. Gall suggests that if you need to build a robust complex system, you should start with a simple, functional system and gradually add complexity. This approach ensures that each layer of complexity is tested and proven before adding more. The recommended progression: - Experiment: Proof of concept or prototype or MVP (or whatever people are calling it these days) - Feedback: Add functionality that is proven to work consistently - Improve: Focus on improving performance and existing functionality before adding new features - Support: Ensure existing functionality can be maintained and supported before adding new features - Slow scaling: Scale organizational processes and structures gradually, ensuring each new layer of complexity is built on a solid foundation of simpler, proven processes. Or in the paraphrased words of Bob P., “The constant urge to be ‘biggering’ should be met with suspicion.”

Reminder: SOPs are not set in stone. They can (and should) be updated and improved over time. This might involve adding additional steps, streamlining a process, or changing steps as you find new software of processes that make life easier. Bonus Tip: Don't be afraid to let your team pitch new ideas for better results and smoother processes. Sometimes, a fresh perspectives will lead to valuable improvements!

From Zero to Automation: Building Our New Project from the Ground Up I'm thrilled to share that we've successfully transformed our new project from a blank slate into a fully automated system! 🚀 Starting with just an idea, our team dived into designing and implementing automation processes that have significantly enhanced our efficiency and productivity. This journey wasn't without its challenges, but seeing the system come to life has been incredibly rewarding. Key Highlights: Strategic Planning: We began by mapping out our goals and identifying areas where automation could make the most impact. Collaborative Effort: Cross-functional teamwork was crucial. Bringing together diverse perspectives helped us create a more robust system. Leveraging Technology: We utilized the latest tools and technologies to ensure our automation processes are scalable and future-proof. Continuous Learning: This project was a learning curve for all of us, emphasizing the importance of adaptability in today's fast-paced environment. I'm proud of what we've achieved and excited about the efficiencies this will bring to our operations. Big shoutout to the amazing team that made this possible! Looking forward to tackling more projects that push the boundaries of what's possible. #Automation #Innovation #TeamSuccess #Productivity #NewProject

I got early feedback that I had written about this topic before because, indeed, I have. Still, this is the most repeated piece of advice I give to managers: in the current industry context, the main improvement you can make to your team is probably ensuring they are working on the right problem. #engineeringmanagement #systemsthinking #vpeng https://lnkd.in/e4B9kk4C

🔓🔑 Discovery: Unlocking Success by Understanding the Problem at hand 💡 Why do we need to build a particular solution? What is the value it will provide to end users? A software solution is successful only if it solves a clear business problem. Defining the problem statement is done by working collaboratively with you to understand the problem we are aiming to solve, and justifying clearly why we are building this software solution. 🛠️💻 What value does this solution provide to your end users? What is your budget? When do you expect to see a return on investing in building this solution? Being able to understand the answers to these questions is an important step in commercially and technically validating with you why it is we are aiming to build this solution. Defining the problem statement is crucial for the Discovery phase in software development due to several reasons: 1️⃣ Clarity and Focus 🎯: A well-defined problem statement helps to clarify what the project aims to achieve. It ensures that everyone involved understands the primary objectives and constraints. 2️⃣ Guiding Decision Making 🛤️: During the Discovery phase a clear problem statement serves as a guide and helps prioritise essential elements and features of the project, helping teams make decisions that align with the core objectives of the project. 3️⃣ Efficiency ⚙️: By clearly defining the problem from the outset, teams can avoid wasting time and resources on irrelevant features or solutions that do not contribute to solving the primary issue. 4️⃣ Stakeholder Alignment 👥: A problem statement ensures that all stakeholders have a unified vision of the project and the steps needed to ensure it achieves its goal. This alignment is crucial for securing buy-in and support throughout the development process, especially when it comes to resource allocation and overcoming project hurdles. 5️⃣ Measuring Success 📊: A clear problem statement allows for the development of specific, measurable objectives that can be used to evaluate the success of the project. Without a clear problem definition, it can be difficult to assess whether the end product effectively addresses the initial concerns. While the word "PROBLEM" seems like a negative, there is nothing negative about clearly understanding why we are building a software solution. Your Problem Statement is the key to discovering success and creating a scalable software project that meets your goals whilst evolving alongside your business needs. #Innovation #Software #Engineering #Discovery #ProblemSolving #ROI #TechLeadership #Collaboration #SoftwareDevelopment