MastodonTech.de

Dr. Karen EilersHow can <a href="https://friends.librescrum.org/tags/research" class="mention hashtag" rel="nofollow noopener" target="_blank">#research</a> and <a href="https://friends.librescrum.org/tags/practice" class="mention hashtag" rel="nofollow noopener" target="_blank">#practice</a> in <a href="https://friends.librescrum.org/tags/Agile" class="mention hashtag" rel="nofollow noopener" target="_blank">#Agile</a> <a href="https://friends.librescrum.org/tags/Software" class="mention hashtag" rel="nofollow noopener" target="_blank">#Software</a> <a href="https://friends.librescrum.org/tags/Development" class="mention hashtag" rel="nofollow noopener" target="_blank">#Development</a> move closer together?This question will be at the heart of a dedicated workshop at XP 2025 – and I’m honored to join as a panel participant.🧩 Workshop title: "Towards a closer collaboration between practice and research in Agile Software Development – What we learnt; and what not?"Agile has come a long way since the 1990s – from a niche software development approach to a catalyst for organization-wide transformation. Yet two persistent gaps remain: ⏳ a time gap between fast-paced change in organizations and the slower pace of academic response 📚 a theory gap regarding long-term adoption and cultural integrationThis workshop, led by Michael Neumann, Maria Rauschenberger, Prof. Dr. Eva-Maria Schön, Tiago Silva da Silva, and Mali Senapathi, aims to address both. We’ll explore how to bridge the divide and build a shared, forward-looking agenda for agile research – grounded in both academic insight and lived practice.💬 The session combines <a href="https://friends.librescrum.org/tags/panel" class="mention hashtag" rel="nofollow noopener" target="_blank">#panel</a> dialogue and hands-on exchange – an invitation to co-create the future of agile transformation together.I look forward to engaging with fellow researchers and practitioners at <a href="https://friends.librescrum.org/tags/XP" class="mention hashtag" rel="nofollow noopener" target="_blank">#XP</a> #2025. Let’s turn collaboration into impact.Want to know more? Visit the XP Website: <a href="https://conf.researchr.org/home/xp-2025" rel="nofollow noopener" translate="no" target="_blank">https://conf.researchr.org/home/xp-2025</a><a href="https://friends.librescrum.org/tags/AgileMethods" class="mention hashtag" rel="nofollow noopener" target="_blank">#AgileMethods</a> <a href="https://friends.librescrum.org/tags/XP2025" class="mention hashtag" rel="nofollow noopener" target="_blank">#XP2025</a> <a href="https://friends.librescrum.org/tags/ResearchPracticeCollaboration" class="mention hashtag" rel="nofollow noopener" target="_blank">#ResearchPracticeCollaboration</a> <a href="https://friends.librescrum.org/tags/AgileSoftwareDevelopment" class="mention hashtag" rel="nofollow noopener" target="_blank">#AgileSoftwareDevelopment</a>

David SabineTip:Avoid creating a heavy <a href="https://mastodon.social/tags/DesignBrief" class="mention hashtag" rel="nofollow noopener" target="_blank">#DesignBrief</a>. Don't overload it with details & unnecessary requirements.Avoid anything that will delay action. It's merely a test of alignment. Are we (likely) on the same page?<a href="https://mastodon.social/tags/DesignThinking" class="mention hashtag" rel="nofollow noopener" target="_blank">#DesignThinking</a> <a href="https://mastodon.social/tags/AgileMethods" class="mention hashtag" rel="nofollow noopener" target="_blank">#AgileMethods</a>

Ulrich JunkerNice critique of <a href="https://fediscience.org/tags/AgileMethods" class="mention hashtag" rel="nofollow noopener" target="_blank">#AgileMethods</a>, <a href="https://fediscience.org/tags/Scrum" class="mention hashtag" rel="nofollow noopener" target="_blank">#Scrum</a> and so on, with suggestions to give more autonomy to developers and to automize as many nasty things as possible. Imho, there is only one receipt to success in <a href="https://fediscience.org/tags/SoftwareDevelopment" class="mention hashtag" rel="nofollow noopener" target="_blank">#SoftwareDevelopment</a>: pose the right questions until you get the right conceptual understanding of the problem to solve and do this problem analysis before doing too much coding. Without good analysis, your code will just be guesswork.<a href="https://youtube.com/watch?v=KJ5u_Kui1sU&si=your" rel="nofollow noopener" target="_blank">https://youtube.com/watch?v=KJ5u_Kui1sU&si=your</a>

Frühere Suchanfragen

Suchoptionen

Verwaltet von:

Serverstatistik:

#agilemethods