Conway's law states that when we design systems those tend to look like our communication structures. It is a bit simplified, but as an example - when we develop a software system using many teams, then the way those teams communicate impacts the way code evolves. If teams talk rarely and not directly, then code reflects that and becomes harder to understand, maintain, produces more defects and so on. When teams talk often and directly, code evolves better, is more consistent and more "pro" if you will. And that reduces future costs. The same applies also to how we design our organizations. If we figure out organizational design details alone or in a small group and then let everyone know, then it looks good on paper and on intranet, but not so in reality. People seem confused, struggling trying to understand and use the magic brainwork. But when we co-create that with others, the organization evolves more naturally and is more accepted by the creators themselves - thus less confusion and struggle, more joy and fun at work. So if you want stuff to actually work and be accepted involve the right people early. This pays back later and lowers costs. It also lowers resistance. And that is actually an old truth: individuals & interactions IS MORE IMPORTANT THAN processes and tools themselves. I guess some Agile people came to that conclusion almost 24 years ago. However, there is a flipside to that: more time & energy is needed. And that is true - involving people and having productive design sessions requires quite a time - preparations, outcomes, formats, etc. And there is one skill behind all that is crucial for those who involve. What is that skill? It is a way older than anything Agile 😃
Ivo Pekšēns’ Post
More Relevant Posts
-
Is your architectural design process bogged down by costly revisions and endless client feedback loops? Agile methodologies, proven effective across various industries, offer a potential solution for streamlining and enhancing architectural projects through a flexible, collaborative approach. Here's how Agile principles could be adapted: 1. Sprint-Based Workflows: In Agile, large tasks are broken down into smaller, manageable "sprints" (typically 2-4 weeks in software development). Architectural sprints might be longer (e.g., 4-6 weeks) to accommodate complexity. Each sprint could focus on a specific phase: conceptual sketches, early-stage plans, or 3D models. This incremental approach allows for regular feedback and quick adjustments. 2. Iterative Design Approach: Instead of a single final design, start with rough prototypes and present iterations regularly to clients for feedback and improvements. This minimizes the risk of costly major revisions and ensures the design aligns with the client's vision throughout the process. 3. Regular Check-ins and Communication: Frequent communication is key. Weekly meetings (adapting the Agile "stand-up" concept) allow for progress assessment, issue resolution, and team alignment. 4. Client Feedback and Flexibility: Active client involvement is crucial. Seek feedback after each sprint to make adjustments and ensure the design meets their needs. 5. Managing the Project Backlog: Maintain a prioritized list of tasks (design revisions, client requests, permits, etc.) to stay organized and track progress. [ Potential Benefits ] Applying Agile principles could lead to increased flexibility, enhanced collaboration, faster revisions, and improved client satisfaction. However, results will vary depending on project specifics and team dynamics. [ Considerations ] Successful Agile implementation in architecture requires careful consideration of project complexity, client engagement, and regulatory constraints. [ Conclusion ] Agile offers exciting potential for improving architectural design, from faster revisions to enhanced collaboration. Have you tried Agile in your design process? I’d love to hear your thoughts or experiences in the comments! Let's connect and discuss further. #Agile #Architecture #Design #ProjectManagement #AgileArchitecture Notice: This post reflects my perspective on applying Agile methodologies to architectural design, based on my project management knowledge. It is not based on formal research in this specific application.
To view or add a comment, sign in
-
Create and improve hardware products faster by using agile design methodology ⏩ Chances are, you’re already using agile methodology to some extent in your product development. In software: Agile design methodology is a project management approach that involves breaking the project into phases and emphasizes continuous collaboration and improvement. In hardware: the product is developed in short iterations of 1-4 weeks. At the end of each iteration, the product is reviewed, tested, and shown to users to gain feedback to feed into the next iteration. This approach can be challenging to the engineering mindset, because engineers typically have high expectations of quality prior to showing their work. BUT faster results require faster methodologies. How does agile benefit hardware development? 1️⃣ Reduce Risk - This approach facilitates early concept validation to ensure the development is aimed in the right direction. It also ensures the final product meets or exceeds customer expectations. 2️⃣ Faster Time to Market - smaller iterations allow 1) getting prototypes into people’s hands faster and 2) keeping the team and investors (all stakeholders) engaged from early on. This quick iteration allows the big-picture development timeline to stay on track. 3️⃣ Flexibility & adaptability- this allows taking into account market changes, requirements changes, and advancements in technology. Short segments of work can be focused on addressing such changes. 4️⃣ Improved collaboration - encourages cross-functional collaboration and communication among stakeholders and customers. It keeps everyone aligned by increasing transparency and encouraging a diverse design feedback loop. ❓ Have you seen a similar approach used in development? #hardware #productdevelopment #conceptdesign #engineering #projectmanagement
To view or add a comment, sign in
-
At Arc 91 Studio, we have consistently faced and overcome various challenges in product and service development through a combination of strategic planning, innovative thinking, and adaptive methodologies. Here are some key strategies we have employed: Comprehensive Market Research and User Feedback: 📊🗣️ Challenge: Understanding market needs and user preferences. Solution: We conduct thorough market research and gather extensive user feedback to ensure our products and services meet the actual needs of our target audience. This involves surveys, focus groups, and beta testing phases to refine our offerings based on real-world input. Agile Development Methodologies:🏃♂️🔄 Challenge: Managing project timelines and adapting to changes. Solution: By adopting agile development methodologies, we can quickly respond to changes and iterate on our products and services. This approach allows us to deliver incremental improvements and maintain flexibility throughout the development process. Cross-Functional Collaboration:🤝💡 Challenge: Ensuring seamless integration of different components. Solution: We foster a collaborative environment where cross-functional teams work closely together. This includes regular meetings and communication between designers, developers, marketers, and other stakeholders to ensure alignment and address any issues promptly. Risk Management and Mitigation:⚠️🛡️ Challenge: Identifying and mitigating potential risks. Solution: We proactively identify potential risks early in the development process and implement mitigation strategies. This includes conducting feasibility studies, prototyping, and stress testing to uncover and address any potential issues before they become critical. Continuous Improvement and Innovation:✨🚀 Challenge: Staying ahead of market trends and technological advancements. Solution: We prioritize continuous improvement and innovation by staying updated with the latest industry trends and technologies. Regular training sessions, attending industry conferences, and encouraging a culture of innovation help us stay ahead of the curve. Customer-Centric Approach:❤️🙌 Challenge: Meeting and exceeding customer expectations. Solution: Our customer-centric approach ensures that we always prioritize the needs and satisfaction of our customers. We maintain open lines of communication with our clients, providing regular updates and incorporating their feedback into our development process. By leveraging these strategies, Arc 91 Studio has successfully navigated the complexities of product and service development, delivering high-quality solutions that meet the evolving needs of our clients and the market.
To view or add a comment, sign in
-
I recently replied to a question on a post about Measuring engineering teams. (linked in comments) asking if there is a better methodology, with scrum's perceived problems. I decided I would make it a full post. I don’t think scrum(or any framework) is good or bad. Characteristics of a High-Performing Team optimizing for fast flow: ♦ Deliver Value Quickly: Deliver meaningful value in short cycles. This includes not just business value but also maintaining quality and enhancing the development experience. ♦ Deliver Quality: Balance fast delivery with the right level of engineering quality, ensuring sustainability, but also considering the timing of business opportunity, when appropriate. ♦ Learn and Adapt: Each iteration brings new learnings that the team uses to improve the next cycle's value delivery. ♦ Responsive to Change: Being agile (in the true sense of the word) means adjusting to change effectively and efficiently. ♦ Create Small as possible stories(work items with clear value): One of the largest contributors to all of the above. ♦ Effective Collaboration: Team members discuss problems regularly, increasing the chances of finding more of the gaps and uncovering ignorance of the problem space together. What Success Looks Like: 🎉 ♦ Sustainable Delivery: The team can consistently deliver value to the business while maintaining team morale and productivity. ♦ Alignment with Business Goals:The team's efforts are connected to broader business objectives. ♦ Minimal Gap in Knowledge of the problem space: Solution adequately match the problem they are trying to solve. ♦ Technical Excellence: Quick delivery does not mean poor quality, once the team knows more about the problem space from a previous iteration they have opportunity to refactor and address necessary tradeoffs made. Whether it's Scrum, Kanban, or even short waterfall cycles, the "best" framework is the one that enables your team to embody these principles. As a manager, your role is to guide your team towards these ideals. It's less about the framework, but more of the pattern of behavior it develops in the team. Visit my site: vanarden.ca
To view or add a comment, sign in
-
As development cycles shorten, effective requirements management becomes more important. The short iteration leads to higher rate changes in requirements, making requirements management more difficult. Therefore, it is more likely to produce bad or incomplete requirements when less time is spent obtaining and verifying requirements. Additionally, there may be more pressure to make decisions quickly, leading to less thorough analysis and validation of requirements. This makes it more difficult to ensure the final solution meets stakeholders' needs. To build the right thing right, Agile development requires the following activities: (1) 𝐄𝐥𝐢𝐜𝐢𝐭 𝐜𝐮𝐬𝐭𝐨𝐦𝐞𝐫 𝐧𝐞𝐞𝐝𝐬: Analyze and validate customer needs, discover customer expectations, and understand customer constraints. (2) 𝐓𝐫𝐚𝐧𝐬𝐟𝐨𝐫𝐦 𝐬𝐭𝐚𝐤𝐞𝐡𝐨𝐥𝐝𝐞𝐫 𝐧𝐞𝐞𝐝𝐬 𝐢𝐧𝐭𝐨 𝐜𝐮𝐬𝐭𝐨𝐦𝐞𝐫 𝐫𝐞𝐪𝐮𝐢𝐫𝐞𝐦𝐞𝐧𝐭𝐬: The system requirements are derived from stakeholder needs, expectations, constraints, and interfaces. (3) 𝐆𝐚𝐭𝐡𝐞𝐫𝐢𝐧𝐠 𝐚𝐧𝐝 𝐝𝐨𝐜𝐮𝐦𝐞𝐧𝐭𝐢𝐧𝐠 𝐫𝐞𝐪𝐮𝐢𝐫𝐞𝐦𝐞𝐧𝐭𝐬 𝐬𝐢𝐦𝐮𝐥𝐭𝐚𝐧𝐞𝐨𝐮𝐬𝐥𝐲: Requirements should be discovered and refined throughout the project, rather than being gathered and documented upfront. (4) 𝐏𝐫𝐢𝐨𝐫𝐢𝐭𝐢𝐳𝐚𝐭𝐢𝐨𝐧 𝐨𝐟 𝐫𝐞𝐪𝐮𝐢𝐫𝐞𝐦𝐞𝐧𝐭𝐬: Requirements are prioritized based on their value to the customer, the team's ability to deliver them, cost and expected quality. (5) 𝐃𝐞𝐟𝐢𝐧𝐢𝐧𝐠 𝐚𝐜𝐜𝐞𝐩𝐭𝐚𝐧𝐜𝐞 𝐜𝐫𝐢𝐭𝐞𝐫𝐢𝐚: Each user story should contain acceptance criteria to ensure the team understands the requirements. (6) 𝐒𝐮𝐩𝐩𝐨𝐫𝐭𝐢𝐧𝐠 𝐐𝐀: To ensure that test cases meet the requirements, test cases must be generated of appropriate quality. (7) 𝐌𝐚𝐧𝐚𝐠𝐢𝐧𝐠 𝐜𝐡𝐚𝐧𝐠𝐢𝐧𝐠 𝐫𝐞𝐪𝐮𝐢𝐫𝐞𝐦𝐞𝐧𝐭𝐬: As requirements change, it's important to adapt quickly and make sure the team knows how the changes will affect the project. (8) 𝐂𝐨𝐥𝐥𝐚𝐛𝐨𝐫𝐚𝐭𝐢𝐨𝐧 𝐰𝐢𝐭𝐡 𝐬𝐭𝐚𝐤𝐞𝐡𝐨𝐥𝐝𝐞𝐫𝐬: Requirements are gathered from a variety of stakeholders. We need to be able to work effectively with all stakeholders to gather and refine requirements and ensure that the team is building the right product. #elicitaterequirements #managingrequirements #requirementengineering
To view or add a comment, sign in
-
AITP Chicago Meeting - 'Innovation Elegance: What a People Centric Methodology Looks Like' 8/22 5:30pm Register: https://lnkd.in/gTHeqjzZ When: Thu, August 22, 2024 5:30 PM - 8:00 PM Location Wood Dale Public Library, 520 N Wood Dale Rd, Wood Dale, IL 60191 Train from Union Station to Wood Dale, using Milwaukee West Cost: AITP, WICySIS members $15, Non-Members $20 Register: https://lnkd.in/gTHeqjzZ You're Invited to an Informational Dinner Meeting A great opportunity to network with your peers! Refreshments: Lots of Pizza, Soft Drinks, Water, etc. Topic: Innovation Elegance - What a People Centric Methodology Looks LIke Innovation has had two decades of software-centric methodologies. Project success rates are not great. The employee experience is not great. What makes innovation difficult is not software, so this should be no surprise. What makes innovation difficult are people – how we interact, collaborate, and compete with each other. Therefore, a people-centric methodology is not revolutionary. It’s just overdue. Your code will be just fine. This session shares five topics (starting with “M”) that shape a people-centric methodology, the how and the why such a methodology is attractive. The metaphors that best describe healthy collaboration The mechanics that govern the most valuable innovation The money profile of low marginal cost The job market’s benefits Mental health benefits Takeaways How and why to adopt a people-centric methodology Enthusiasm and confidence to adopt a new methodology Sanity, safety, and self-respect whether you’re pursue this or not AITP or WiCyS Member: $15 Non-Member: $20 Bio: Robert Snyder Robert Snyder is the founder and president of Innovation Elegance, LLC. Robert’s thirty-year career spans roles such as developer, project management, change management, sales enablement, and the performing arts. His career path includes corporate roles, consulting roles, startups, PMP, and Agile certifications. He’s performed in numerous vocal, dance, and theater ensembles. Robert earned his BS in Electrical Engineering from the University of Illinois and his MBA in Strategy from the Kellogg School of Management at Northwestern University. Robert is publishing a series of books on innovation methodology. “Innovation Elegance: Transcending Agile with Ruthlessness and Grace” (available now) “Innovation Portfolio: Five Verbs Shape Your Team’s Legacy” (available now) “Elegant Leadership: Distinguishing the Good, the Bad, and the False” (targeting 2025)l
To view or add a comment, sign in
-
𝗗𝗿𝗶𝘃𝗶𝗻𝗴 𝗔𝗱𝗮𝗽𝘁𝗮𝗯𝗶𝗹𝗶𝘁𝘆 𝗮𝗻𝗱 𝗮 𝗖𝘂𝗹𝘁𝘂𝗿𝗲 𝗼𝗳 𝗜𝗻𝗻𝗼𝘃𝗮𝘁𝗶𝗼𝗻 Jeff Winter once said, "𝙏𝙝𝙚 𝙛𝙪𝙩𝙪𝙧𝙚 𝙗𝙚𝙡𝙤𝙣𝙜𝙨 𝙩𝙤 𝙩𝙝𝙤𝙨𝙚 𝙬𝙝𝙤 𝙖𝙘𝙩 𝙬𝙞𝙩𝙝 𝙪𝙧𝙜𝙚𝙣𝙘𝙮 𝙖𝙣𝙙 𝙛𝙤𝙧𝙚𝙨𝙞𝙜𝙝𝙩." How can we architects push the envelope, drive transformative change, and ensure that our company thrives? Here are 3 strategies architects can use to drive adaptability and cultivate a culture of innovation in their organizations: 𝟭/ 𝗣𝗿𝗼𝗺𝗼𝘁𝗲 𝗖𝗼𝗻𝘁𝗶𝗻𝘂𝗼𝘂𝘀 𝗟𝗲𝗮𝗿𝗻𝗶𝗻𝗴 𝗮𝗻𝗱 𝗘𝘅𝗽𝗲𝗿𝗶𝗺𝗲𝗻𝘁𝗮𝘁𝗶𝗼𝗻 Encourage a mindset of continuous learning and experimentation within your teams. Push for training, workshops, and learning that keep everyone updated on the latest technologies. Run hackathons and innovation days where teams experiment with new ideas and technologies without the pressure of immediate results. This approach nurtures a culture where innovation is seen as the norm. A constant pursuit and not just a one-time effort. 𝟮/ 𝗠𝗮𝗸𝗲 𝗖𝗿𝗼𝘀𝘀-𝗙𝘂𝗻𝗰𝘁𝗶𝗼𝗻𝗮𝗹 𝗖𝗼𝗹𝗹𝗮𝗯𝗼𝗿𝗮𝘁𝗶𝗼𝗻 𝗛𝗮𝗽𝗽𝗲𝗻 Break down silos by promoting cross-functional collaboration. Create opportunities for teams from different departments to work together on projects and share insights. Use collaborative tools and platforms to facilitate communication and knowledge sharing. Bringing diverse perspectives together fosters creativity and drives innovative solutions. Architects are in a unique position to lead by example, showing how collaborative efforts can lead to breakthroughs and more adaptable solutions. 𝟯/ 𝗘𝘅𝗰𝗲𝗹-𝗲𝗿𝗮𝘁𝗲 𝗔𝗴𝗶𝗹𝗲 𝗠𝗲𝘁𝗵𝗼𝗱𝗼𝗹𝗼𝗴𝗶𝗲𝘀 Excel at agile methodologies to enhance flexibility and responsiveness. Agile practices allow teams to quickly respond to changes and refine their approaches (...𝘢𝘯𝘥 𝘥𝘰𝘯'𝘵 𝘴𝘬𝘪𝘱 𝘺𝘰𝘶𝘳 𝘳𝘦𝘵𝘳𝘰𝘴!). By embedding agile principles into the architecture practice, architects can help teams become more adaptable and better equipped to handle uncertainties. This adaptability is crucial for maintaining a competitive edge in a rapidly changing environment. By promoting continuous learning and experimentation, facilitating cross-functional collaboration, and implementing agile methodologies, architects can drive adaptability and cultivate a culture of innovation in their organizations. These strategies enhance the organization's ability to respond to change and position it for sustained growth and success. ________ 👍 Like if you enjoyed this. ♻️ Repost to empower your network. Follow Kevin Donovan for more. ________ 🚀 Join the IT Architects' Hub! Unlock more 3-𝙖𝙘𝙩𝙞𝙤𝙣𝙖𝙗𝙡𝙚-𝙩𝙞𝙥𝙨 with our coming newsletter. We aim to connect you with a community that gets it. Dive into a network of peers who challenge the status quo. Ready to level up? Improve your skills, meet peers, and elevate your career! Click and Subscribe 👉 https://lnkd.in/dgmQqfu2 -- Photo by Silas Baisch
To view or add a comment, sign in
-
Agile Organization Design: Moving Beyond Size Logic https://lnkd.in/dcvyXnmJ
To view or add a comment, sign in
-
“Just enough design** to make decisions **evidence + analysis + hypothesis + measurement + iteration = design” I’m working on something that’s new and complex. Complex in setup (multi-disciplinary collaboration within specific governance structures), complex in the outcomes it aims to deliver (and that we have to develop greater evidence and aims for those, fast), most importantly it requires insight and inclusion of complexity for people’s lived experience and support they need (without building in exclusion.) We just can’t bite off all that to chew on in one giant analysis process with 30 team members in the first few weeks, (or even the first 8 weeks if I’m honest.) I’ve spent 4 weeks in pre discovery identifying tensions and writing principles for how we collaborate and this is one of them… we had been struggling with multiple people arriving in the team, dumping their projects, problems, solutions and opportunities on the table and it was disproportionately impacting any sense-making work ahead of analysis . So I tried to describe a proportionate approach that reassured people that the iteration matters most, that we weave in the next part of the problem space faster if we have a manageable amount (of the problem space) in the sprint we’re in… Sharing for discussion, augmentation, disagreement. (it’s not an exhaustive list or intended as fixed description) HT to Annie Heath who posted last week about the all the roles she and her teams play in user centred design - reminding me we need to talk more about the design doings. ALSO! I need a scrum master that can create new multi-discipline ways of working in public sector, generate structure that reassure and include senior leaders… and grow the role to lead multiple teams towards designing, engineering and delivering outcomes for people (happy to chat to agile folks, no agency please)
To view or add a comment, sign in
-
https://lnkd.in/eWfV4N5Y Has anyone read about the "Impact Engineering" approach? This article says it seems to outperform agile 🤷♂️ It seems initial requirements are very important for success.
'Impact Engineering' development approach outperforms Agile
https://www.developer-tech.com
To view or add a comment, sign in