Podcasts about Requirements engineering

BONUS: Tom Gilb on Building True Engineering Culture and Delivering Value Through Evolutionary Methods In this BONUS episode, we dive deep into the world of true engineering discipline with Tom Gilb, a pioneer who was writing about Agile principles before Agile was even named. We explore his latest book "Success - Super Secrets & Strategies for Efficient Value Delivery in Projects and Programs, and Plans" and uncover the fundamental flaws in how organizations approach project delivery and stakeholder management. The Genesis of Success-Focused Engineering "People were failing at project deliveries - even when using Agile. I saw there was very little about setting clear goals and reaching them, it had nothing to do with being successful." Tom's motivation for writing his latest book stems from a critical observation: despite the widespread adoption of Agile methodologies, project failure rates remain unacceptably high. The core issue isn't methodology but rather the fundamental lack of clarity around what success actually means. Tom emphasizes that true success is about achieving the improvements you want at a price you can afford, yet most organizations fail to define this clearly from the outset. In this segment, we refer to the book How Big Things Get Done by Bent Flyvbjerg who published statistics on the poor performance of projects in general. Beyond OKRs: The Power of Quantified Multi-Dimensional Objectives "First you need to have a definition of what it means to succeed. And that needs to be multi-dimensional. And you need to clarify what they are." While many organizations believe they're already quantifying objectives through frameworks like OKRs, Tom reveals significant weaknesses in these approaches. True value isn't just profit—it encompasses multiple dimensions including security, usability, and other stakeholder-specific benefits. The key insight is learning to quantify what needs to be achieved across all critical dimensions, as you simply cannot design for high-quality attributes like security without first quantifying and designing for them explicitly. In this segment, we talk about Tom's paper on OKR's titled "OKR Objectives and Key Results: what's wrong and how to fix it". The Missing Engineering Discipline "Why is the failure rate of our projects so high?" Tom identifies a paradoxical problem: engineering organizations often lack true engineering discipline. This fundamental gap explains why project success rates remain low despite technological advances. Real engineering requires systematic approaches to design, stakeholder analysis, and incremental value delivery—disciplines that are often overlooked in favor of rushed implementations. Stakeholder Analysis: Beyond User Stories "Stakeholders have a requirement - even if we don't know it. They might be people, but also law, contract, policies, etc. They all have requirements for us." Traditional user-centered methods like user stories can lead to failure when critical stakeholders are overlooked. Tom advocates for comprehensive stakeholder analysis as the foundation of engineering discipline. Stakeholders aren't just people—they include laws, contracts, policies, and other constraints that have requirements for your system. The practical tip here is to use AI tools to help identify and list these stakeholders, then quantify their specific requirements using structured approaches like Planguage. The Gilb Cycle: True Incremental Value Delivery "Get things done every week, next week, until it's all done. We need to decompose any possible design into enough increments so that each increment delivers some value." What distinguishes Tom's evolutionary approach from popular Agile frameworks is the focus on choosing the most efficient design and then systematically improving existing systems through measured increments. Each increment must deliver tangible value, and the decomposition process should be aided by AI tools to ensure optimal value delivery. This isn't just about iteration—it's about strategic improvement with measurable outcomes. Building Engineering Culture: A Two-Leader Approach "There are two leaders: the tech leaders and the management leaders. For management leaders: demand a value stream of results starting next week. To the tech leaders: learn the engineering process." Creating a true engineering culture requires coordinated effort from both management and technical leadership. Management leaders should demand immediate value streams with weekly results, while technical leaders must master fundamental engineering processes including stakeholder analysis and requirement quantification. This dual approach ensures both accountability and capability development within the organization. Further Resources During this episode we refer to several of Tom's books and papers. You can see this list below Software Metrics by Tom Gilb Principles of software engineering management - Also available in PDF Evo book   About Tom Gilb Tom Gilb, born in the US, lived in London, and then moved to Norway in 1958. An independent teacher, consultant, and writer, he has worked in software engineering, corporate top management, and large-scale systems engineering. As the saying goes, Tom was writing about Agile, before Agile was named. In 1976, Tom introduced the term "evolutionary" in his book Software Metrics, advocating for development in small, measurable steps. Today, we talk about Evo, the name that Tom used to describe his approach. You can link with Tom Gilb on LinkedIn.

Diesmal sind wir in Bielefeld und mit Nils Müller von der OEDIV, einem Tochterunternehmen der bekannten Oetker-Gruppe tauchen wir in die faszinierenden Herausforderungen der Digitalisierung des deutschen Mittelstands ein. Als Rückgrat der deutschen Wirtschaft ist der Mittelstand zwar eine tragende Säule, aber nicht als großer Treiber der Digitalisierung bekannt. Wir sprechen darüber, was den Mittelstand charakterisiert, wie Daten zunehmend zu einem Erfolgsfaktor werden und warum es eigentlich immer um den Pudding geht.

Es gibt viele Wege ein Problem zu lösen, doch wie würdest du es tun?Softwareentwicklung ist weit mehr als nur Programmieren. Es geht darum, das eigentliche Problem zu verstehen, sich zu fragen, ob dies wirklich ein Problem ist und ob es sich (in Bezug auf den Aufwand) lohnt, dieses Problem zu lösen und wie man es lösen würde. Verschiedene Lösungswege zu durchdenken, die Vor- und Nachteile abzuwägen und final die beste Entscheidung zu treffen, ist einer der größten Skills von erfahrenen Softwareentwickler*innen.In dieser Episode machen wir genau das: Eine Art Design- bzw. Architektur- bzw. Implementierungs-Diskussion. Wir stellen die Frage “Wie würdest du folgendes Problem lösen und implementieren?”. Das Szenario ist dabei eine Art Preis-Monitor. Ähnlich wie Geizhals oder Idealo, doch deutlich simpler.Bonus: Brauchen wir ein Cron-Package in jeder Programmiersprache?Unsere aktuellen Werbepartner findest du auf https://engineeringkiosk.dev/partnersDas schnelle Feedback zur Episode:

Listen to this interview of Marcos Kalinowski, Professor, Department of Informatics, Pontifical Catholic University of Rio de Janeiro, Brazil; and also, of Daniel Mendez, Full Professor, Blekinge Institute of Technology, Sweden, and head of Requirements Engineering at fortiss, Germany. We talk about starting a new track at a prestigious journal, with all the challenges and triumphs such a venture brings. Daniel Mendez : "The reviewing and publishing of research is also a social process. And I know that Marcos and me edit looking for reasons to accept, instead of to reject a submission. And we are privileged to work with reviewers who share our approach to research publishing." Learn more about your ad choices. Visit megaphone.fm/adchoices Support our show by becoming a premium member! https://newbooksnetwork.supportingcast.fm/new-books-network

Listen to this interview of Marcos Kalinowski, Professor, Department of Informatics, Pontifical Catholic University of Rio de Janeiro, Brazil; and also, of Daniel Mendez, Full Professor, Blekinge Institute of Technology, Sweden, and head of Requirements Engineering at fortiss, Germany. We talk about starting a new track at a prestigious journal, with all the challenges and triumphs such a venture brings. Daniel Mendez : "The reviewing and publishing of research is also a social process. And I know that Marcos and me edit looking for reasons to accept, instead of to reject a submission. And we are privileged to work with reviewers who share our approach to research publishing." Learn more about your ad choices. Visit megaphone.fm/adchoices

In dieser Folge des #ITundTECH Podcasts spricht Holger Winkler mit Simon Jiménez, Gründer von storywise, über die Herausforderungen des Requirements Engineering im Allgemeinen und wie das Anforderungsmanagement in der Softwareentwicklung deutlich einfacher wird mit der neuen Software storywise. Das sind die Themen des Interviews im Detail:Die Probleme des Anforderungsmanagements bei der Softwareentwicklung.Unzulängliche Pflichtenhefte: Das Grundproblem hinter vielen scheiternden Softwareprojekten. Wie die Requirements-Engineering-Software storywise bei der Sammlung und Dokumentation von strukturierten Anforderungen für die Softwareerstellung viel Zeit und Energie spart.Für wen eignet sich storywise und wie wird die Nutzung abgerechnet?Die Requirements-Engineering-Software storywise in Detail.Abonnieren Sie unseren Kanal, um auf dem neuesten Stand zu bleiben!Weiterführende Informationen zur Firma ireo GmbH / storywise:► Internet: https://storywi.se/ ► LinkedIn-Firmenseite: https://www.linkedin.com/company/ireo-storywise/ ► Simon Jiménez auf LinkedIn: https://www.linkedin.com/in/simon-a-t-jimenez/ —Der Werbepartner dieser Sendung: „Mitarbeiter werben Mitarbeiter auf LinkedIn" - 3 x effizienter als Facebook- oder LinkedIn-Ads ► Internet inkl. kostenlosem Quick-Check: https://www.itundtechjobs.com/ —Über den #ITundTECH für Deutschland Podcast:Der Podcast mit CEOs innovativer Softwarehersteller, IT-Dienstleister oder TECH-Unternehmen aus Deutschland!► Abonniere unseren Youtube-Kanal: https://www.youtube.com/@itundtech ► Abonniere unseren Podcast: https://www.itundtech.de/podcast ► Besuche uns auf unserer Webseite: https://www.itundtech.de/ ► Vernetze dich mit Holger Winkler auf LinkedIn: https://www.linkedin.com/in/holger-winkler/—Sie sind CEO eines innovativen Unternehmens aus dem IT- und TECH-Umfeld und hätten Lust, als Gast in den ITundTECH für Deutschland Podcast eingeladen zu werden?Dann melden Sie sich hier: https://www.itundtech.de

Listen to this interview of Darja Smite, Professor of Software Engineering at Blekinge Institute of Technology, Sweden, and also research scientist at SINTEF; and, Jarle Hildrum, Director, Deloitte Consulting, Norway; and also, Daniel Mendez, Professor of Software Engineering at Blekinge Institute of Technology, Sweden, and as well, Senior Scientist heading the research division Requirements Engineering at fortiss. We talk about their paper Work-from-home is here to stay: Call for flexibility in post-pandemic work policies (JSS 2023). Daniel Mendez : "Two key takeaways from our collective experience here are, No.1, figures don't need to be absolute — so, we should really focus on the essence of what we want to convey. And No.2, in terms of what we want to convey, I think that every figure ideally has one key message, one key takeaway." Learn more about your ad choices. Visit megaphone.fm/adchoices Support our show by becoming a premium member! https://newbooksnetwork.supportingcast.fm/new-books-network

Listen to this interview of Darja Smite, Professor of Software Engineering at Blekinge Institute of Technology, Sweden, and also research scientist at SINTEF; and, Jarle Hildrum, Director, Deloitte Consulting, Norway; and also, Daniel Mendez, Professor of Software Engineering at Blekinge Institute of Technology, Sweden, and as well, Senior Scientist heading the research division Requirements Engineering at fortiss. We talk about their paper Work-from-home is here to stay: Call for flexibility in post-pandemic work policies (JSS 2023). Daniel Mendez : "Two key takeaways from our collective experience here are, No.1, figures don't need to be absolute — so, we should really focus on the essence of what we want to convey. And No.2, in terms of what we want to convey, I think that every figure ideally has one key message, one key takeaway." Learn more about your ad choices. Visit megaphone.fm/adchoices Support our show by becoming a premium member! https://newbooksnetwork.supportingcast.fm/sociology

Listen to this interview of Darja Smite, Professor of Software Engineering at Blekinge Institute of Technology, Sweden, and also research scientist at SINTEF; and, Jarle Hildrum, Director, Deloitte Consulting, Norway; and also, Daniel Mendez, Professor of Software Engineering at Blekinge Institute of Technology, Sweden, and as well, Senior Scientist heading the research division Requirements Engineering at fortiss. We talk about their paper Work-from-home is here to stay: Call for flexibility in post-pandemic work policies (JSS 2023). Daniel Mendez : "Two key takeaways from our collective experience here are, No.1, figures don't need to be absolute — so, we should really focus on the essence of what we want to convey. And No.2, in terms of what we want to convey, I think that every figure ideally has one key message, one key takeaway." Learn more about your ad choices. Visit megaphone.fm/adchoices Support our show by becoming a premium member! https://newbooksnetwork.supportingcast.fm/economics

Listen to this interview of Darja Smite, Professor of Software Engineering at Blekinge Institute of Technology, Sweden, and also research scientist at SINTEF; and, Jarle Hildrum, Director, Deloitte Consulting, Norway; and also, Daniel Mendez, Professor of Software Engineering at Blekinge Institute of Technology, Sweden, and as well, Senior Scientist heading the research division Requirements Engineering at fortiss. We talk about their paper Work-from-home is here to stay: Call for flexibility in post-pandemic work policies (JSS 2023). Daniel Mendez : "Two key takeaways from our collective experience here are, No.1, figures don't need to be absolute — so, we should really focus on the essence of what we want to convey. And No.2, in terms of what we want to convey, I think that every figure ideally has one key message, one key takeaway." Learn more about your ad choices. Visit megaphone.fm/adchoices

Karl Wiegers, Principal Consultant with Process Impact and author of 14 books, and Candase Hokanson, Business Architect and PMI-Agile Certified Practitioner at ArgonDigital, speak with SE Radio host Gavin Henry about software requirements essentials. They explore five different parts of requirements engineering and how you can apply them to any ongoing project. Wiegers and Hokanson describe why requirements constantly change, how you can test that you're meeting them, and why the tools you have at hand are suitable to start straight away. They discuss the need for requirements in every software project and provide recommendations on how to gather, analyze, validate, and manage those requirements. Candase and Karl offer in-depth perspectives on a range of topics, including how to elicit requirements, speak with users, get to the source of the business or user goal, and create requirement sets, models, prototypes, and baselines. Finally, they look at specifications you can use, and how to validate, test, and verify them. Brought to you by IEEE Computer Society and IEEE Software magazine.

Robert Briese: Beyond Requirements, Rethinking Agile Product Ownership Read the full Show Notes and search through the world's largest audio library on Scrum directly on the Scrum Master Toolbox Podcast website: http://bit.ly/SMTP_ShowNotes. The Great Product Owner: Impact Mapping And Other Tools Great POs Use To Focus On Outcomes In this episode, Robert discusses the attributes of a great Product Owner based on an energy company's experience. The exemplary PO managed a budget, aimed to introduce new products, and emphasized impactful market presence. The PO's coachability and commitment to improvement are highlighted, along with insights from Marty Cagan's "Inspired." A great PO, as outlined, prioritizes impact over outputs, maintains clarity on product goals and business vision, and employs tools like Impact Mapping for outcome-focused development. The Bad Product Owner: Beyond Requirements, Rethinking Agile Product Ownership In this episode, Robert identifies Product Owner (PO) anti-patterns, emphasizing that many POs don't truly own a product. A common pitfall is when POs isolate themselves, detailing requirements independently and presenting them to the team for feedback. This approach creates a significant gap between development teams and POs, limiting the focus to "delivering requirements." The episode recommends a shift in approach, encouraging POs to step away from detailed isolation and instead bring direct customer/end-user information to development teams.   [IMAGE HERE] Are you having trouble helping the team work well with their Product Owner? We've put together a course to help you work on the collaboration team-product owner. You can find it at bit.ly/coachyourpo. 18 modules, 8+ hours of modules with tools and techniques that you can use to help teams and PO's collaborate.   About Robert Briese Robert Briese, is an Agile Coach who's seen it all. From startup stumbles to orchestrating massive Large-Scale Scrum feats, like BMW's level 3 autonomous driving milestone. He's on a mission to simplify the complex and help teams build adaptable, sustainable organizations. Buckle up for a wild, Agile ride with Robert! You can link with Robert Briese on LinkedIn and connect with Robert Briese on Twitter. 

Tom Siebeneicher: The Agile Product Owner, The Necessary Adaptation of PO to a New Team Read the full Show Notes and search through the world's largest audio library on Scrum directly on the Scrum Master Toolbox Podcast website: http://bit.ly/SMTP_ShowNotes. The Great Product Owner: The Software Designer PO Anti-pattern In this episode, Tom highlights anti-patterns like a lack of trust in the team's judgment and over-explanation of implementation details. Tom offers a valuable tip of using stories to illustrate the distinction between "how" and "why" for effective communication. He underscores the importance of clearly defining Acceptance Criteria (ACs) while avoiding dictating the solution's appearance. Tom also emphasizes the need for coaching efforts directed towards the team's understanding and collaboration, demonstrating the reciprocal nature of the Product Owner role. The Bad Product Owner: The Art of Adaptation, The Necessary Adaptation of PO to a New Team Tom delves into the nuances of an effective Product Owner (PO). Tom shares a cautionary tale of a PO's performance shift after changing teams, emphasizing the importance of aligning behavior with team needs. He advises against expecting uniformity and highlights the role of self-awareness in fostering an environment of growth and effectiveness. He emphasizes the need to adapt PO behaviors between different teams, underscoring the need for refined communication. Prioritization, a crucial aspect, is explored in depth.    [IMAGE HERE] Are you having trouble helping the team work well with their Product Owner? We've put together a course to help you work on the collaboration team-product owner. You can find it at bit.ly/coachyourpo. 18 modules, 8+ hours of modules with tools and techniques that you can use to help teams and PO's collaborate. About Tom Siebeneicher Tom is an engaging speaker, who has delivered presentations at conferences like the Atos DREAM Conference, the Agile Leadership Day, and TED XKE by Xebia. Their enthusiasm for discussing Agile is evident in those talks. You can link with Tom Siebeneicher on LinkedIn.   

Andrew Mitchell: Communication, and Empowering Engineers, Two Product Owner Superpowers Read the full Show Notes and search through the world's largest audio library on Scrum directly on the Scrum Master Toolbox Podcast website: http://bit.ly/SMTP_ShowNotes. The Great Product Owner: Marty Cagan's Influence, Inspiring Excellence in Product Ownership In this segment, Andrew emphasizes the importance of moving POs out of engineering and into the business to better understand business needs. Inspired by Marty Cagan's book “Inspired”, this great PO excelled in writing effective stories and facilitated closer collaboration between developers and customers. They viewed the engineers' involvement with customers as a helpful aid rather than a threat. This shift toward self-management empowered the team and enabled faster delivery of products. A great PO plays a crucial role in fostering collaboration, understanding business requirements, and driving successful outcomes. The Bad Product Owner: The PO that could not communicate requirements effectively, and what to do about it In this segment, Andrew discusses the challenges that arise from having a bad Product Owner (PO). These POs excel in discovery but struggle to communicate effectively with the team, leading to frustration and a lack of trust. Andrew suggests coaching the POs in writing clear stories and focusing on value and prioritization. Interrupting the team's work is another issue to avoid. He emphasizes the importance of well-defined acceptance criteria in stories. Andrew also notes that problems with bad POs often stem from organizational issues rather than individual skills. Bringing the team closer to the discovery work can help address these challenges effectively.   [IMAGE HERE] Are you having trouble helping the team work well with their Product Owner? We've put together a course to help you work on the collaboration team-product owner. You can find it at bit.ly/coachyourpo. 18 modules, 8+ hours of modules with tools and techniques that you can use to help teams and PO's collaborate.   About Andrew Mitchell Andrew prioritizes people when building products, aiming for happy and engaged employees who create great products and serve customers well. He emphasizes trust, psychological safety, servant leadership, and believes Scrum is the best framework to achieve these goals. He was also a host of the Product Owner Summit 2023, where we collaborated. You can link with Andrew Mitchell on LinkedIn.

Susan and Scott discuss requirements engineering and business analysis. Our guest is Stan Buehne from the International Requirements Engineering Board (IREB). IREB is a nonprofit organization based in Germany that focuses on promoting and improving the discipline of requirements engineering. Stan discusses the importance of requirements engineering in various industries, such as automotive, aviation, and medical domains. He emphasizes the need for precision and accuracy in documenting requirements to ensure the development of high-quality solutions. Requirements engineering also involves managing and handling changing requirements over time. The conversation touches on the term "engineering" in requirements engineering and its association with the discipline's focus on precise documentation and creating shared understanding between stakeholders, developers, and architects. The discussion also explores: the relevance of requirements engineering in agile environments and the need for value-oriented documentation and risk reduction the difference between user requirements and system requirements, as well as functional requirements and non-functional requirements the impact of AI on requirements engineering, both in terms of AI supporting the requirements engineering process and the challenges of validating AI-generated content the alignment of requirements engineering with the agile mindset RESOURCES: - IREB https://www.ireb.org - Glossary https://www.ireb.org/en/cpre/glossary/ - Requirements Management Tools https://makingofsoftware.com/resources/list-of-rm-tools/ Business Analysis Live is hosted by: - Susan Moore, Community Engagement Manager at IIBA - Scott Bennett, Manager, Business Analysis at IIBA Do you have questions about this topic or have an idea for a different topic? Ask us a question at live@iiba.org or leave us a voice message on our podcast homepage. The International Institute of Business Analysis (IIBA) is a non-profit professional association serving the field of business analysis.  As the global thought leader and voice of the business analysis community, IIBA actively supports the recognition of the profession, and works to maintain global standards for the ongoing development of the practice and certifications.  Learn more at https://www.iiba.org/  #businessanalysis #requirementsengineering #IREB --- Send in a voice message: https://podcasters.spotify.com/pod/show/iiba-org/message

Markus wrote an interesting article about the topic. Machine learning (ML) is used increasingly in real-world applications. In this paper, we describe our ongoing endeavor to define characteristics and challenges unique to Requirements Engineering (RE) for ML-based systems. As a first step, we interviewed four data scientists to understand how ML experts approach elicitation, specification, and assurance of requirements and expectations. The results show that changes in the development paradigm, i.e., from coding to training, also demands changes in RE. Thanks for listening. We welcome suggestions for topics, criticism and a few stars on Apple, Spotify and Co. We thank our new partner [Siemens ](https://new.siemens.com/global/en/products/automation/topic-areas/artificial-intelligence-in-industry.html) Our guest: Markus Borg ([more](https://www.linkedin.com/in/mrksbrg/)) **Shownotes:** The article Markus mentioned ([more](https://arxiv.org/abs/1908.04674))

Daniel Westermayr: The problem with cluttered backlogs and how to declutter them, coaching Product Owners Read the full Show Notes and search through the world's largest audio library on Scrum directly on the Scrum Master Toolbox Podcast website: http://bit.ly/SMTP_ShowNotes. In this episode, Daniel Westermayr discusses his belief in the importance of the Scrum Master role in helping companies achieve their product goals. He shares his experience of encountering a cluttered backlog with items that were years old and how he cleaned it up, only to face complaints from someone in support. Daniel emphasizes the need for Scrum Masters to clarify why a large backlog is a problem, and why the company wants to keep all items. He also advises that Scrum Masters should understand what they stand for and constantly question why certain practices are being implemented. Finally, he suggests that, in order to avoid fears of losing important information, the older requirements can be stored in a safe location. Daniel also mentions an article on how to declutter product backlogs.   [IMAGE HERE] Recovering from failure, or difficult moments is a critical skill for Scrum Masters. Not only because of us, but also because the teams, and stakeholders we work with will also face these moments! We need inspiring stories to help them, and ourselves! The Bungsu Story, is an inspiring story by Marcus Hammarberg which shows how a Coach can help organizations recover even from the most disastrous situations! Learn how Marcus helped The Bungsu, a hospital in Indonesia, recover from near-bankruptcy, twice! Using Lean and Agile methods to rebuild an organization and a team! An inspiring story you need to know about! Buy the book on Amazon: The Bungsu Story - How Lean and Kanban Saved a Small Hospital in Indonesia. Twice. and Can Help You Reshape Work in Your Company.   About Daniel Westermayr Daniel is a Kanban Trainer with a knack for all things Lean and Theory of Constraints. He wants to help teams achieve and measure their continuous improvements. You can link with Daniel Westermayr on LinkedIn. 

For international women's day, we spoke with two academics of colour about their experiences of being minority women in academia.   Henrika McCoy is the Ruby Lee Piester Centennial Fellow in Services to Children and Families and associate professor at the Steve Hicks School of Social Work at the University of Texas at Austin. Henrika shares her experience of colleagues and students having erroneous expectations about her scholarship and background because she is a Black female academic. And she addresses the assumption that non-parent academics don't have any caring responsibilities.  More from Henrika: Diversity statements: the good, the bad and the ugly Questions you should ask yourself about your role in institutional racism Yes, your university perpetuates racism against BAME academics: what can you do? Didar Zowghi is a professor of software engineering and a senior principal research scientist at CSIRO's Data61. She leads a research team in "Diversity and Inclusion in AI" and "Requirements Engineering for Responsible AI". She is also the leader of the National AI Centre's think tank on diversity and inclusion in AI in Australia, emeritus professor at University of Technology Sydney and conjoint professor at the University of New South Wales. Didar speaks about about biases in AI systems, improving the gender imbalance among AI professionals and her journey from Iran to the upper echelons of the AI research community.   

Find out how to go from writing good to great requirements in this webinar recording episode presented by Fernando Valera, Visure Solutions' CTO. Requirements Specification is a critical part of the Requirements Engineering process for any industry. Clear and concise requirements specification is very important because it serves as the foundation for all future work on the project. Hence, it is essential to follow a systematic and chronological structure for the requirements documents. Furthermore, there are certain aspects that are a must when writing great requirements. So, how can you ensure that your requirements documents are not just good but great? Join our Member Portal for FREE & Gain full access to more exclusive Interviews, Webinar recordings, exclusive Whitepapers and early access to Requirements Engineering Methodology courses. Create your FREE account here. Want to Learn More About Our Requirements Specification Course? Click here. Read Episode Article. Watch Full Video Episode here. Begin gaining end-to-end Traceability with Visure Requirements ALM Today. Start 30-Day Free Trial.

Dr. Nils Becker, Usability Experte am Johner Institut, berichtet im Gespräch mit Professor Johner von den typischen Schwierigkeiten, auf die die Hersteller bei der Entwicklung gebrauchstauglicher Medizinprodukte stoßen. Das sind nicht nur regulatorische Hürden, sondern auch die Wahl der Methoden beim Requirements Engineering sowie bei der formativen und summativen Evaluation. Dr. Becker stellt die regulatorischen Anforderungen vor und gibt Tipps aus seiner Praxis als Leiter von zwei Usability Laboren in Deutschland und den USA.

Episode description*Conspiracy Walls in Requirements Engineering: Analyzing Requirements like a Detective - Paper von Anne Hess zu spannenden, alternativen RE Ansätzen - Digitale Dörfer: Digitalisierung in ländlichen Regionen nutzen und spannende User Research Erkenntnisse dazu - Empathy Mapping: Eine Übersicht erstellen darüber, was Nutzer:innen denken, sagen und fühlen - Wie man ein Drehbuch schreibt: Ein schön illustriertes "How to", welches auch für UX Designer ein spannender Einstieg ins Storytelling sein kann - User Requirements Engineering gepaart mit Storytelling: LeanScope als UX Management Tool für einen narrativen, kontinuierlichen Ansatz Mehr zu Centigrade: www.centigrade.de www.linkedin.com/company/centigrade-gmbh/ www.instagram.com/centigradegmbh

Thomas Immich, CEO der UX Agentur Centigrade, trifft Markus Trapp vom IESE und spricht über folgende Themen: Was genau hat es mit dem brandneuen Berufsbild des Digital Design Professionals (DDP) auf sich und welchen Platz nehmen UX Design oder Industriedesign dabei ein? Ach ja... und was hat das mit meinen Kollegen bei Centigrade zu tun, die - wie ich - bei gutem Wetter im Amarillo Outdoor Workspace arbeiten? Diesen und weiteren spannenden Fragen habe ich mich im allerersten Outdoor Interview meiner Reihe #UXOutOfTheBuilding gewidmet. Debütant war dabei mein Gast Marcus Trapp, der u.a. als Co-Autor des DDP Handbuches bei der Definition des Berufsbildes mitgewirkt hat und deshalb tief aus dem Nähkästchen plaudern kann. Marcus arbeitet im Bereich Digital Innovation Design beim Fraunhofer IESE in Kaiserslautern und ist Experte für Requirements Engineering und Digitale Ökosysteme. Und hier noch die wichtigsten Organisationen, Menschen und Werke, die unseren Interview-Flow - retrospektiv betrachtet - doch maßgeblich beeinflusst hatten: - "The Timeless Way of Building" von Christopher Alexander zur Frage was Architektur mit Software Entwicklung zu tun hat. - Der "Second System Effect" aus dem Buch "The Mythical Man Month" von Fred Brooks als hoch-interessante Feststellung, dass die zweite, disruptiv bessere Version eines Systems in der Regel zum Scheitern verurteilt ist. - Die berühmt-berüchtigte "German Angst" und ihre Auswirkung darauf, wie wir Deutschen inzwischen zu Innovationen gelangen - oder eben gerade nicht. - Die Geschichte des Innovators und Entrepreneurs Jeff Hawkins, der während der Prototyping Phase des Palm Pilot ein simples Stück Holz verwendet hat, um seine Annahmen zu verifizieren. - Natürlich auch die offizielle Digital Design Professional Website, die u.a. die Zertifizierung zum "DDP Foundation Level" anbietet (https://www.digitaldesign.org/) sowie die IREB GmbH, welche die offizielle Dachorganisation hinter dem DDPs ist (https://www.ireb.org/) und innerhalb von Deutschland von der BITKOM e.V. unterstützt wird. An alle weiteren Köpfe hinter dem DDP, also u.a. Kim Lauenroth, David Gilbert und Stan Bühne: wenn ihr wichtige Dinge ergänzen möchtet, seid ihr herzlich eingeladen, die Kommentare unter diesem Post zu nutzen oder - noch besser - selbst als Gast zum Outdoor Interview zu kommen... solange es das Wetter noch zulässt. Fühlt euch eingeladen!

Zu Gast in dieser Folge ist Andreas Vogelsang, Professor für Requirements Engineering an der Uni Köln. Andi klärt uns erst mal über das deutsche System für Professuren auf und wie das für ihn mit Familie zusammenging. Er erzählt außerdem was denn eigentlich Requirements Engineering ist und warum man es doch als eher deutsche Disziplin bezeichnen kann. Da Andi auch einige Jahre mit der Software deutscher Autohersteller gearbeitet hat, gibt er anschließend noch spannende Einblicke in deren Systeme und klärt was sich in dem Markt gerade alles tut.Chair for Software & Systems Engineering an der Uni Köln: https://cs.uni-koeln.de/sse Forschung im Bereich Requirements Engineering:Requirements Engineering for ML: https://arxiv.org/pdf/1908.04674.pdfPrediction of Risks in RE: https://arxiv.org/pdf/2007.03358.pdf

Das Handwerk im Systems-Engineering und Requirements-Engineering zu erlernern ist nicht einfach und erfordert harte Arbeit. Nichts im Leben ist einfach, speziell, wenn es darum geht, als Systemingenieur komplexe Probleme zu lösen. Zusammen habe ich mit ehemaligen Kollegen 1,5 Jahre investiert, um ein funktionsfähiges und tragfähiges Konzept aufzustellen, mit dem Systeme effizient entwickelt werden können. Nichts von dem was ich hier weitergebe, ist das absolute Patentrezept. Es gibt keine einzig wahre Methode oder magisches Tool, um ein Entwicklungsprojekt besser zu machen. Ich verstehe mich als Systemingenieur aus der Praxis für die Praxis und gebe meine Erfahrung weiter. Es bedeutet eine Menge harter Arbeit, um hervorragende Systeme zu entwickeln. Warum also diese Folge? Du vermeidest Sackgassen indem ich Dir über die Schulter blicke und passenden Rat zur passenden Zeit gebe. In fünf Modulen begleite ich Dich bei der Einführung dieses schwierigen Themas.

Zur 100. Folge haben wir uns ein kleines Experiment ausgedacht und wollen Menschen, die uns in den letzten zwei Jahren begleitet haben wieder zu Wort kommen lassen. Dazu haben ihnen wir ihnen diese Fragen gestellt: - Was ist Deiner Meinung nach das (nächste) wichtigste Thema in den kommenden 12 Monaten, welches wir in der Produktmanager/Product Owner-Community diskutieren werden? - Was ist der eine Satz, den du am liebsten jedem/r Product Owner:in mitgeben möchtest? - Was wünscht Du uns Produktwerkern für die kommenden 100 Folgen? In dieser Folge werden wir daher viele ehemalige Gäste wieder hören und halten uns selbst mal etwas zurück. Wenn ihr nach der Folge mehr über unsere Gäste in dieser Folge erfahren wollt, und Lust auf eine ganze Folge mit ihnen habt, findet ihr hier nun die ganzen Links :-) Sohrab Salimi (https://www.scrum-academy.de/trainers/sohrab-salimi/) - Apr 2020 Product Owner als Agile Leader (https://produktwerker.de/product-owner-als-agile-leader/) - Feb 2021 Auf Business oder Nutzer fokussieren als PO? (https://produktwerker.de/business-oder-nutzer/) Indra Burkart (https://www.youtube.com/c/indraburkart) - Mai 2021 Mit Customer Journey Maps arbeiten (https://produktwerker.de/customer-journey-maps/) Johannes Schartau (https://de.linkedin.com/in/johannes-schartau) - Mai 2020 Wie Liberating Structures Dir als Product Owner helfen (https://produktwerker.de/mit-liberating-structures-als-product-owner-zombie-scrum-entkommen/) Katja Busch (https://de.linkedin.com/in/katja-busch-525b9820) - Apr 2021 Die Relevanz von UX den eigenen Stakeholdern vermitteln (https://produktwerker.de/die-relevanz-von-ux-vermitteln/) Tim Herbig (https://herbig.co/) - Nov 2020 Outcome Goals und Product Discovery (https://produktwerker.de/outcome-goals-product-discovery/) Steffi Götten (https://www.linkedin.com/in/steffi-g%C3%B6tten/) - Aug 2020 Dein Freund der Scrum Master (https://produktwerker.de/dein-freund-der-scrum-master/) Heiko Stapf (https://www.emendare.de/team/heiko-stapf/) - Feb 2020 Welche Rolle sollte Product Discovery in der Arbeit von Product Ownern spielen? (https://produktwerker.de/welche-rolle-sollte-product-discovery-in-der-arbeit-von-product-ownern-spielen/) Sabina Lammert (https://de.linkedin.com/in/sabina-lammert-14abb512b) - Jul 2020 Visual Leadership für Product Owner (https://produktwerker.de/visual-leadership-product-owner/) Björn Schotte (https://de.linkedin.com/in/bjoernschotte) - Dez 2019 Der Product Owner aus Sicht eines Dienstleisters (https://produktwerker.de/der-product-owner-aus-sicht-eines-dienstleisters/) - Nov 2020 Product Owner im skalierten Umfeld (https://produktwerker.de/product-owner-im-skalierten-umfeld/) Eva-Maria Schön (https://de.linkedin.com/in/evamariaschoen) - Juni 2020 Requirements Engineering im Agilen meistern (https://produktwerker.de/agiles-requirements-engineering-meistern/) Boris Steiner (https://www.borissteiner.com/) und Glenn Lamming (https://www.glennlamming.com/) - Jun 2021 Evidence Based Management (https://produktwerker.de/evidence-based-management/) Vielen Dank für eurer Interesse und auf die nächsten 100 und mehr Folgen. :-)

Von schlechten Anforderungen haben wir alle bereits gehört! Aber, was können Softwarearchitekt:innen tun, um bessere Anforderungen zu erhalten? Und, sollten sich Softwarearchitekt:innen mit dem Thema Anforderungsanalyse beschäftigen? Spoiler: Die Antwort ist: “Ja”. In dieser Episode werden diese und mehr Fragen von Gernot Starke und Peter Hruschka beantwortet. Links Leanpub Buch zu Requirements Engineering Peter Hruschkas Buch zu Requirements Engineering iSAQB Advanced Modul Lehrplan bei GitHub IREB Folge zu DSL

Durch das Refinement wird das Product Backlog zu einem gut gepflegten Product Backlog und ist dadurch ein wichtiges Werkzeug für Product Owner. Tim und Dominique unterhalten sich in dieser Folge über das Refinement des Product Backlogs und welche Bedeutung es für uns als Product Owner hat. Zu Beginn klären wir erst einmal, was Refinement eigentlich ist und wie es in Scrum passt. Das Refinement wird zwar oft als Termin gesehen, ist aber eigentlich ein Prozess. Deshalb sprechen wir über den allgemeinen Ablauf des Refinements, wer alles mitwirkt und was wir als Product Owner vorbereiten sollten. Wir sind nämlich davon überzeugt, dass wir neben Vision und Product Goal auch eine aktuelle Roadmap dabei haben sollten. Dank dem Refinement haben wir dann nicht nur ein gepflegtes Product Backlog; wir erhalten auch neuen Input für die Priorisierung von Product Backlog Items und erlangen ein Verständnis über Umfang, Kosten, Risiken und anderer Aspekte der ganzen Backlog Items. Wir können daher dank des Refinements bessere Entscheidungen treffen. Und wie in jeder Folge wollen wir mit ein paar Tipps abschließen. Habt ihr beispielsweise mal daran gedacht das Refinement eines bestimmten Themas als Product Backlog Item einzuplanen, damit im nächsten Sprint an diesem Thema gearbeitet wird? In der Folge erwähnen wir übrigens kurz das Product Backlog Refinement Canvas, eine gut geeignete Vorlage, um sich eine strukturierte Übersicht zu machen. Ihr findet es unter https://www.kaizenko.com/the-product-backlog-refinement-canvas/ Wenn ihr noch mehr über das Product Backlog hören wollt, dann empfehlen wir euch die folgenden Folgen: - Das Product Backlog (https://produktwerker.de/product-backlog/) - Ist dein Product Backlog voll bzw. zu groß? (https://produktwerker.de/product-backlog-voll/) - Product Backlog Einträge sind nicht nur User Stories! (https://produktwerker.de/product-backlog-eintraege/) Wenn euch dieser Podcast gefällt, freuen wir uns auch über eine positive Bewertung in eurer Podcast App oder als Feedback per Mail an podcast@produktwerker.de oder via Instagram oder Twitter (@produktwerker).

Das Aufteilen (sog. Splitting) von User Stories erscheint oft als eine der schwierigsten agilen Praktiken für Product Owner. Letztlich ist es aber eine Frage der Übung. In dieser Episode besprechen Tim und Oliver "Übungen", um diesen "Muskel" zu trainieren. Es geht also zum Strategien, wie man gute Schnitte zum Aufteilen von User Stories finden kann. User Stories fühlen sich oft zu groß an, um sie in einem Sprint fertig zu stellen. Es ist aber unser Ziel, in regelmäßigen Abständen sinnvolles Feedback zu erhalten, um im komplexen Umfeld in möglichst kurzen Zyklen zu lernen, was unser Produkt wertvoll macht. Vielen Product Ownern und Teams fällt es jedoch schwer, (zu) große User Stories bzw. Features in gute, kleine Stories aufzuteilen. Wir suchen daher immer nach vertikalen Schnitten, so dass wir nach ihrer Umsetzung ein hilfreiches Feedback auf das neue Produktinkrement erhalten können. Wir besprechen u.a. die folgenden Fragen: - Wann sind User Stories "zu groß"? - Prinzipien und Kriterien beim Aufteilen von User Stories - Strategien und Muster, um gute Schnitte zu finden - Stolperfallen beim Schneiden von User Stories - Grenzen beim Story Splitting: manchmal geht's halt nicht - was dann? Quellen zum Story Splitting Im Gespräch beziehen wir uns auf die folgenden Quellen: - INVEST in Good Stories von Bill Wake (https://xp123.com/articles/invest-in-good-stories-and-smart-tasks/) - 10 powerful strategies for breaking down Product Backlog Items in Scrum (with cheatsheet) von Christiaan Verwijs (https://link.medium.com/z8nCpZSyx9) - Twenty Ways to Split Stories von Bill Wake (https://xp123.com/articles/twenty-ways-to-split-stories/) - User Story Splitting Flowchart von Richard Lawrence. Deutsche Fassung übersetzt von Kai Simons (https://www.ksimons.de/2012/09/user-stories-einfach-teilen-mit-dem-user-story-splitting-flowchart/) - S.P.I.D.R. Approach von Mike Cohn (https://www.mountaingoatsoftware.com/exclusive spidr-poster-download) Im Zusammenhang mit User Story Splitting sind auch weitere Folgen rund um das Product Backlog Management und vor allem in Bezug auf User Stories und andere Product Backlog Elemente empfehlenswert: - Erfolgreich mit User Stories arbeiten - Akzeptanzkriterien richtig einsetzen - Arten von Product-Backlog-Einträgen: Was gibt's neben User Stories noch? - Feature Breakdown: schnell User Stories finden und grob schätzen - Wie können wir den Erfolg von User Stories messen? Wie läuft das Aufteilen von Anforderungen bzw. das Schneiden von zu großen User Stories bei Euch ab? Wir freuen uns, wenn du deine eigenen Erfahrungen mit uns in einem Kommentar auf unserer Webseite (https://produktwerker.de/user-story-splitting/) oder auf unserer Produktwerker LinkedIn-Seite teilst. Wenn euch die Folge gefällt, freuen wir uns über eine positive Bewertung in eurer Podcast App oder als Feedback per Mail an podcast@produktwerker.de oder via Instagram oder Twitter.

Wir brauchen kein Requirements Engineering mehr. Wir sind jetzt agil! Stimmt das? Ich habe vor ca. 10 Jahren ein Coaching beim Thema Anforderungen und Anforderungsreviews erhalten und gelernt, wie Anforderungen sprachlich ausgedrückt werden können, damit der Entwickler auch genau das umsetzt, was man sich vorstellt. Nach diesen 10 Jahren wollte ich wissen, ob durch sich durch die Agilisierung alles verändert hat und das Thema Requirements Management überhaupt noch Bedeutung hat. Du erhältst Antworten auf die Fragen, - wie Du Anforderungen EINDEUTIG formulieren kannst, - wie Du die Anforderungsqualität überprüfen kannst - was Du tust, wenn das Lasterhaft und Pflichtenheft final sind und dann Change Request reinkommen. ... und vieles mehr.

Mich beschäftigt immer wieder die Frage, wie passen Requirements Engineering (RE) und Scrum eigentlich zusammen. Können diese beiden Bereiche überhaupt zusammenspielen und sich gegenseitig unterstützen? In der heutigen Folge #67 spreche ich mit Kim Lauenroth über dieses Thema und als Leiter des Competence Centers für RE bei adesso und Vorstand des IREB, dem International Requirements Engineering Board ist er somit der ideale Ansprechpartner, um auf das Zusammenspiel von RE und Scrum zu schauen. Link Website:  https://cutt.ly/scrummeistern67

Sascha Brossmann ist Consultant und Inhaber von &:create Product Leadership. Zusammen mit Dr. Jörg Dörr schildert er die Probleme mit heutigen Produkten, die bezüglich Produktethik und Nachhaltigkeit aufkommen können.

Sascha Brossmann ist Consultant und Inhaber von &:create Product Leadership. Zusammen mit Dr. Jörg Dörr schildert er die Probleme mit heutigen Produkten, die bezüglich Produktethik und Nachhaltigkeit aufkommen können.

In dieser Folge spricht Dominique mit Eva-Maria Schön über die Herausforderungen des agilen Requirement Engineering und wie wir sie als Product Owner meistern können. Zu den großen Herausforderungen gehören die Abhängigkeiten zu anderen Teams, die Selbstständigkeit der Teams, ein fehlender Blick auf das große Ganze, die kontinuierliche Pflege von Anforderungen, Anforderungn von den Nutzern einsammeln und das Einbinden der Stakeholder. (Siehe dazu auch https://www.researchgate.net/publication/316116540_Key_Challenges_in_Agile_Requirements_Engineering). Mehr über Eva findet ihr auf LinkedIn: https://de.linkedin.com/in/evamariaschoen Wir sind gespannt zu hören, wie Ihr als Product Owner ein agiles Requirement Engineering einsetzt und welche Erfahrungen ihr dabei gesammelt habt. Wie immer freuen wir uns über Euer Feedback auf produktwerker.de, per Mail an podcast@produktwerker.de oder via Twitter an @produktwerker.

In this episode, our host and experts discuss two factors from The Standish Group Report that may have a significant effect on the success of a project.

Digitalisierung ist auch das Aufräumen der Bestandssysteme. Johannes Richter von der HALLESCHE Krankenversicherung a.G. spricht über die Notwendigkeit des Standardisierens, Aktualisierens und Wegwerfens.

Für diese Revision holten sich Schepp, Peter und Rodney Unterstützung von Yara Meyer (Principal Consultant bei , auf Twitter @whythecode) in Studio, um die Untiefen der Projektplanung zu erforschen. …

Für diese Revision holten sich Schepp, Peter und Rodney Unterstützung von Yara Meyer (Principal Consultant bei , auf Twitter @whythecode) in Studio, um die Untiefen der Projektplanung zu erforschen. Schaunotizen [00:01:28] Requirements Engineering, Agilität und Wasserfälle Yara hat im Rahmen ihres Schaffens als Consultant schon so manches mehr oder weniger erfolgreiches Projekt begleitet und quatscht […]

Jesko Schneider von der Anforderungsfabrik stellt die zentralen Herausforderungen für Agilität in komplexeren Projekten vor und gibt Auskunft, worauf dabei zu achten ist.

Freunde der Qualität, wir begrüßen Euch zu unserer 9. Podcast-Ausgabe! Christian Brandes, Team Lead Requirements Engineering bei QualityMinds, tauscht sich mit seiner Kollegin Rebecca Schönberger darüber aus, wie ein „agiles RE“ konkret aussehen könnte und sollte, was man damit erreichen kann und warum so viele Projekte und Unternehmen mit diesem Thema offenbar immer noch so große Schwierigkeiten haben. Viel Spaß dabei! Sprecher: Christian Brandes: www.xing.com/profile/Christian_Brandes11 Rebecca Schönberger: www.xing.com/profile/Rebecca_Schoenberger Ressourcen online: Christians Folien auf der ModernRE-Konferenz 2018: www.modern-re.de/files/modernre/site/vortraege2018/tag3/Do2.3_Christian_Brandes-ModernRE2018_Brandes_AgilesRE.pdf User Stories sind keine Requirements: www.scrumexpert.com/knowledge/user-stories-are-not-requirements/ https://jaxenter.de/scrum-user-stories-78154 Ron Jeffries’ CCC-Prinzip: http://ronjeffries.com/xprog/articles/expcardconversationconfirmation/ Product-Canvas-Beispiel: www.romanpichler.com/blog/the-product-canvas/ Agile Testing Quadrants: lisacrispin.com/2011/11/08/using-the-agile-testing-quadrants/ Über QualityMinds: www.qualityminds.de twitter.com/qualitymindsde Feedback & Themenwünsche an: Zu dieser Folge: requirements@qualityminds.de

Eduard Groen ist User Experience und Requirements Engineer beim Fraunhofer IESE. In unserem Podcast verrät er uns Details aus seinen Forschungen zum Crowd-Based-Requirements-Engineering

Senior Usability Expert Dr. Kerstin Röse von der Siemens AG gibt uns einen Einblick ins Requirements Engineering 4.0, das RE der Zukunft. Wie das Requirements Engineering sich den Herausforderungen der Digitalisierung stellen kann, erklärt sie im Podcast.

In Podcast Folge Nr. 59 geht's um das wichtige Thema "Requirements Engineering". Christian und Bernhard erläutern zunächst, was darunter zu verstehen ist, was dieses Thema im eHealth-Podcast zu suchen hat und gehen dabei kurz auf die Phasen im RE-Prozess ein. Zuvor gibt es wie immer ein paar News, die u .a. den Fahrplan eAkte der Bundesregierung, die Paracelsus Klinik der Zukunft und die Alexa Health Skills beinhalten.  Links Fahrplan eAkte (Ärztezeitung) EPA der AXA (Ärzteblatt) Alexa Health Skills (Health Policy Online) Paracelsus Klinik der Zukunft (KMA) Antwort der Bundesregierung auf Anfrage der Grünen Das Kano-Modell zur Bewertung von Anforderungen - Youtube-Video Lehrbuch Software Requirements von Ulrike Hammerschall und Gerd Beneken Requirements-Engineering und -Management Anforderungsermittlung – Hellsehen für Fortgeschrittene Basiswissen Requirements Engineering von Klaus Pohl und Chris Rupp Requirements Engineering - Fundamentals Principles & Techniques Klaus  Pohl Usability und UX kompakt von Michael Richter und Markus D. Flückinger

Prof. Dr. André Schekelmann von der Hochschule Niederrhein spricht über seine internationale Studie zum Requirements Engineering: "Naming the Pain in Requirements Engineering".

Ich bin im Gespräch mit Dr. Stefan Queins. Wir unterhalten uns darüber, was ist SysML und wie es mir mitt Requirements Engineering zusammenhängt. Außerdem beleuchten wir die Fragen, wie ich zur System Architektur komme, wer eigentlich die Modelle erstellen muss und wer muss sie nur lesen? Zum Schluss sprechen wir darüber, wann ist eine Einführung SysML sinnvoll ist und was ich bei der Einführung SysML beachten muss.

Mittlerweile wird mehr oder weniger überall nach agilen Methoden Software entwickelt. Diese Vorgehensweise hat natürlich nicht nur Auswirkungen auf einzelne Teams und deren Prozesse, sondern beeinflusst früher oder später Unternehmensbereiche und irgendwann die Organisation als Ganzes. Überall muss über Anpassungen und Änderungen nachgedacht werden, so auch beim Thema "Requirements Engineering", also der Art und Weise, wie Anforderungen in die Entwicklung gelangen. Und genau das ist das Thema dieser Episode.

Dr. Jörg Dörr (Fraunhofer IESE) spricht mit Anika Peter von der Cosmos Direct Versicherung über Requirements Engineering aus Kundenperspektive. Dabei geht es vor allem darum, inwieweit User Experience und Design Thinking mit RE zusammenhängen.

Wie unterscheidet sich eigentlich Requirements Engineering im agilen Umfeld zum Requirements Engineering für komplexe mechatronische Systeme? Ich bin im Gespräch mit Michael Mahlberg und wir beleuchten, warum Requirements Engineering im agilen Umfeld gemacht wird. In der Episode erfährst du, warum auch im agilen Umfeld Requirements Engineering betrieben wird. Wir beleuchtet, was für unterschiede es gibt und wo wir Gemeinsamkeiten haben.

So wirst du in der Episode wirst du erfahren was das RE-Camp ist und wie du davon profitieren kannst.

In dieser Folge spreche ich mit Nicole Hartl darüber, warum dokumentierte Geschäftsprozesse so wichtig für IT-Anforderungen sind und wie man diese dafür sinnvoll nutzt. Nicht erst seit dem großen Trend der Digitalisierung verfolg das Business Process Management ein großes Ziel: die Automatisierung von Geschäftsabläufen. Um dieses Thema haben sich viele Disziplinen gebildet, wie z.B. Anforderungsmanagement, Demand Management oder Requirements Engineering. Gleich bei allen ist, dass die Basis immer der Geschäftsprozess ist. Nicole Hartl – Expertin für Anforderungsmanagement – erklärt, worauf es ankommt.

In episode #38 I have already had the pleasure to welcome Joachim Reinke. Joachim is an expert in requirements engineering. In episode 38 he explained the reasons why we definitely need requirements engineering. And today I'm happy that we managed to continue our talk. We're discussing the big pain points in Requirements Engineering. And how it is possible to relief this pain. But we also needed to back up a little bit to grab the bigger picture. First we identified the main points in Requirements Engineering. In a second step we jumped into the details how to select an appropriate tool to support you in maintaining requirements. It's not that easy to find the right tool. Because there a several aspects you need to consider. For example you will regularly not establish such a tool on the greenfield. There will be environmental conditions, limitations and constraints which might bother you. And here's Joachim's list of 9 important bullets when selecting a RE-tool will become very helpful.

Learn the importance of developing security requirements in the same time frame as functional requirements.

"We do not need specificiation because our product is its own specification!" You know such kind of statements? You suffer from such kind of attitudes? Then you're exactly right in this tech-chat with Joachim Reinke. Joachim is an elaborated specialist for such kind of hassle. He is an engineer who specialized in the area of Requirements Engineering. He's a crack in this area of the development and production process. We both got acquainted at the systems camp 2016 in Berlin. Requirements engineering refers to defining, documenting and maintaining requirements to the sub-fields of systems engineering and software engineering. But the major question is - why does it seem that neglected in real development life. We're discussing a lot about these aspects. The benefits you get out of well done requirements engineering are tremendous. But it's also a quite long way to go. However also the longest way starts with the first step. In this episode we're giving you the path to do the first steps and continue successfully. Stay with me and enjoy the chat.

Requirements Engineering spielt in jedem Entwicklungsprozess eine wichtige Rolle. In der agilen Software-Entwicklung kommt ihm eine besondere Bedeutung zu.

In dieser Episode sprechen wir mit Stefan Sturm über den unterschiedlichen Aufbau der beiden Vereine IREB und IIBA, den Unterschied zwischen Business-Analyse und Requirements Engineering und warum diese beiden Disziplinen (und Vereine) einander brauchen.

Probleme verstehen, Lösungsansätze erarbeiten und einem Unternehmen zu helfen, Ziele zu erreichen - das ist die Mission der Rolle des Business Analysten. Dazu bedient er sich verschiedenster Methoden, u.a. auch der Anforderungserhebung, -analyse und -management. Aber ist Business Analyse nur eine andere Umschreibung für Requirements Engineering oder doch etwas vollkommen anderes? Ist eine Differenzierung dieser beiden Disziplinen notwendig oder künstlich? Wie sehen die Gemeinsamkeiten aus, wie definieren BA und RE jeweils ihren Scope, wo sehen die Experten ihre jeweilige Rolle angesiedelt und mit welchen Vorurteilen haben sie in Unternehmen zu kämpfen?

From the BuildStuff Conference 2013, we bring you an interview with Tom Gilb. Tom is the author of nine published books, and hundreds of papers on Agile and related subjects. His latest book ‘Competitive Engineering’ (CE) is a detailed handbook on the standards for the 'Evo' (Evolutionary) Agile Method, and also for Agile Spec QC. The CE book also, uniquely in the Agile community, defines an Agile Planning Language, called 'Planguage' for Quality Value Delivery Management. His 1988 book, Principles of Software Engineering Management (now in 20th Printing) is the publicly acknowledged source of inspiration from leaders in the Agile community (Beck, Highsmith, and many more), regarding iterative and incremental development methods. In this interview Tom speaks about how software development should be value driven, and how to go about achieving it. Follow Tom on twitter: @imtomgilb This interview was recorded on the 10th of December 2013 at the BuildStuff conference in Vilnius. Interview by @freekl and @ArneTim Links for this podcast: For lists of books and papers by Tom and Kai Gilb visit their website on Gilb.com Quantify the un-quantifiable: Tom Gilb at TEDxTrondheim (Video) Agility is the Tool, not the Purpose, Presentation at the AgileByExample conference 2013 Book: Principles of Software Engineering Management, Tom Gilb, 1988 Book: Competitive Engineering: A Handbook For Systems Engineering, Requirements Engineering, and Software Engineering Using Planguage. Tom Gilb, 2005 This podcast is in English - Deze podcast is in het Engels

The network equipment industry is being driven towards Software-Defined Networking (SDN), a technology transition that threatens to commoditize network equipment. With a cast of established networking giants, hot start-up companies, and other formidable players, there is a dynamic and complex competitive landscape, with billions of dollars at stake. Network Equipment Manufacturers (NEMS) will need to effectively execute their product strategies to either protect or seize market share and margins. This means establishing close alignment and responsiveness to customer needs and requirements, and then having the agility to deliver the corresponding software capabilities and products. Paridhi Verma and Harvey Wong, speakers.

Dr. McCoy and the medical tricorder device from Star Trek is becoming reality. Entrepreneurs, start-ups, and traditional medical device manufacturers are leveraging the compute power, portability, and connectivity of Smartphones to create a new class of medical diagnostic devices. There's even an X Prize competition adding fuel to the market interest. This podcast discusses the regulatory compliance considerations and the key product development lifecycle practices that are needed to build Smartphone-based medical devices. Paridhi Verma, Harvey Wong and Martin Bakal, speakers.

Diagnostic Grifols has adopted Agile practices while keeping development in compliance with regulations. In this podcast you will learn how Diagnostic Grifols has evolved its practices with the new AAMI's Technical Information Report (TIR45) which gives guidance on the use of Agile in medical device development; Diagnostic Grifols has attained significant gains in productivity with a simultaneously Agile and compliant approach; and how this type of approach could be used in other regulated industries as well. Keith Collyer and Paridhi Verma, speakers.

Engineering medical devices is not an easy job. These devices include an increasing amount of software that integrates with hardware and electronics and need to meet changing healthcare needs and standards. This podcast will discuss how IBM Rational solution for medical devices provides tools to meet regulatory compliance with enhanced automation and reporting to avoid audits, lawsuits and company collapse, manage product complexity by integrate requirements and quality management and reduce time-to-market and cost by early defect detection and removal. Keith Collyer and Paridhi Verma, speakers.

For most medical device companies, the design control requirements of the FDA, as defined in 21 CFR Part 820, are fundamental to the business of developing products. The challenge is how to ensure that you remain compliant to these regulatory needs while reducing the overhead in doing so. Ideally, you want to make compliance just part of "how we do business around here", and, in effect, invisible to the practitioners. This podcast will discuss approaches to make that possible. Marty Bakal and Paridhi Verma, speakers.

Heavily regulated industries like automotive, aerospace and defense, and medical devices face issues like requirements management and traceability across the lifecycle to meet regulatory needs. While for lightly regulated industries like Telecom and consumer electronics key issues are being able to reuse components from product to product as development time frames get shorter. These industries have to address these pain points through their entire supply chain in developing both hardware and software. This podcast will focus on IBM Rational solutions for development of hardware/software co-design. Marty Bakal and Paridhi Verma, speakers.

Welcome to the Software Process and Measurement Cast 190! The SPaMCAST 190 features my interview with Raja Bavani. We discussed distributed agile! Raja Bavani is Chief Architect of MindTree’s Product Engineering Services (PES) and IT Services (ITS) groups and plays the role of agile evangelist. He has more than 20 years of experience in the IT industry and has published papers at international conferences on topics related to Code Quality, Distributed Agile, Customer Value Management and Software Estimation.  His IT experience started during the early 90s, when he was involved in porting a leading ERP product across various UNIX platforms. Later he moved onto products that involved data mining and master data management. During early 2000, he worked with some of the niche independent software vendors in the hospitality and finance domains.  At MindTree, he has worked with some of the top vendors of virtualization platforms, business service management solutions and health care products.  His areas of interests include Global Delivery Model, Agile Software Development, Requirements Engineering, Software Architecture, Software Reuse, Customer Value Management, Knowledge Management, and IT Outsourcing.  He is a member of IEEE and IEEE Computer Society.  He regularly interfaces with educational institutions to offer guest lectures and writes for technical conferences.  Also, he writes for magazines such as Agile Record, Cutter IT Journal and SD Times.   He blogs on Distributed Agile at http://www.mindtree.com/blogs/author/raja-bavani Raja's blog on Software Engineering and his articles and white papers are available at http://se-thoughtograph.blogspot.com He can be reached at raja_bavani@mindtree.com Shameless Ad for my book!  Mastering Software Project Management: Best Practices, Tools and Techniques co-authored by Murali Chematuri and myself and published by J. Ross Publishing. We have received unsolicited reviews like the following: "This book will prove that software projects should not be a tedious process, neither for you or your team." News just in  . . . We also just got word that the SPM book has been adopted for a class at the University of West Flroida for the Fall. Have you bought your copy? Contact information for the Software Process and Measurement CastEmail:  spamcastinfo@gmail.comVoicemail:  +1-206-888-6111Website: www.spamcast.netTwitter: www.twitter.com/tcagleyFacebook:  http://bit.ly/16fBWV Next The Software Process and Measurement Cast 191 will return to my essay "Who Owns Agile Estimation."

Welcome to the Software Process and Measurement Cast 126 SPaMCAST 126 features my interview with Phillip A. LaPlante discussing his book Requirements Engineering for Software and Systems in specific and requirements in general.  A real powerhouse discussion of requirements. Dr. Phil Laplante is Professor of Software Engineering at Penn State. His interests are in software and systems engineering, project management, and software testing and security. Prior to his academic career Dr. Laplante spent several years as a software engineer and project manager working on avionics, computer aided design and software test systems. He has authored or edited 27 books and has published more than 200 scholarly papers. Recently, he was named by the National Council of Engineering Examiners to Chair the committee that will develop the examination, which will be used to license Professional Engineers in the practice of Software Engineering. Laplante received his B.S., M.Eng., and Ph.D. in Systems Planning & Management, Electrical Engineering, and Computer Science, respectively, from Stevens Institute of Technology and an MBA from the University of Colorado. He is a Fellow of the IEEE and SPIE and a member of numerous other professional societies, program committees, and boards. He is a licensed professional engineer in Pennsylvania and a Certified Software Development Professional. Email: plaplante@gv.psu.eduWebsite: http://www.personal.psu.edu/pal11/ Remember: This podcast will post at the beginning of the SEPG NA in Portland, Oregon, March 21-24, 2011 http://www.sei.cmu.edu/sepg/na/2011/index.cfm  I will be attending the conference and manning the David Consulting Booth.   Look me up! I will be speaking at the QAI Quest 2011 in Boston April 6 - 8 http://www.qaiquest.org/boston/If you are attending and would like to get together just drop me a note, text, tweet or phone call! Shameless Ad for my book! Mastering Software Project Management: Best Practices, Tools and Techniques co-authored by Murali Chematuri and myself and published by J. Ross Publishing. We have received unsolicited reviews like the following: "This book will prove that software projects should not be a tedious process, neither for you or your team." Have you bought your copy? Contact information for the Software Process and Measurement CastEmail:  spamcastinfo@gmail.comVoicemail:  +1-206-888-6111Website: www.spamcast.netTwitter: www.twitter.com/tcagleyFacebook:  http://bit.ly/16fBWV Next!SPaMCAST 127 I will  begin reading my paper on PMOs in an Agile Organization titled "Agile is from Venus and PMOs are from Mars". I promise . . . unless less another topic demands that I address it!  

Welcome to the Software Process and Measurement Cast 125! I recorded this Cast before the earthquake in Japan but did want to let all of the SPaMCAST friends and all of the people of Japan that my thoughts are with you.  In this week’s Software Process and Measurement Cast I feature a short entry I wrote on coaching, a comment on the blog entry on coaching and two calls to action.  The paper on Agile is from Venus and PMOs from Mars will begin in SPaMCAST 127.  The essay begins . . . Coaching is a core agile technique, however the impact of the differing coaching technique has not been thoroughly understood which has meant that practices were driven based on individual style.  That is until now.    Why is coaching important?  Coaching is important because it can lead it to smoothly functioning organizations; higher productivity and profits. Call to Action One:Last year I interviewed Bertrand Meyer about SEMAT (see SPaMCAST 96 at www.SPAMCAST.libsyn.com). During the interview he indicated that one the reasons he was participating was to find a means to bridge the gap between practitioners and academia. The idea that there was a gap has been weighing on my mind since, to a great or lesser extent.  So why do you think there is a gap?  Is the gap (if it exists) driven by distrust or is that practitioners do not value input from academics?  Your thoughts and ideas will help me frame a future essay. Call to Action Two and Book Plug . . .Many Software Process and Measurement Cast Listeners have purchased Mastering Software Project Management: Best Practices, Tools and Techniques co-authored by Murali Chemuturi and myself and published by J. Ross Publishing.  Thank you!  If you are one of those many listeners, please consider posting a review on Amazon or one of the many online book review sites.  Reviews help sell books.  So if you agreee with Robert C. Anderson, Director, Process Development and Quality Assurance, Computer Aid, Inc that "Mastering Software Project Management is a masterpiece of clarity, organization and depth of practical knowledge" why not let the world know with a review? Finally do want me to sign a bookplate for your copy of the book?  Email me and include a picture of you with your copy of the book and I will send you a personalized, signed bookplate! Contact information for the Software Process and Measurement CastEmail:  spamcastinfo@gmail.comVoicemail:  +1-206-888-6111Website: www.spamcast.netTwitter: www.twitter.com/tcagleyFacebook:  http://bit.ly/16fBWV Check out my blog and show notes for upcoming conferences and webinars! Next!In SPaMCAST 126 I will feature my interview with Phillip A. LaPlante on his book Requirements Engineering for Software and Systems.  This was a powerhouse interview on requirements; you will not want to miss it.

Welcome to the Software Process and Measurement Cast 82! The interview in the SPaMCAST 82 is with Cheryl Jones.  We discussed Practical Software and Systems Measurement.  Can you say measurement or even more loudly MEASUREMENT!  PSM is an evolving force in the IT measurement field.  Cheryl helps us understand why measurement is important for projects and management. Cheryl Jones is a lead software engineer in the Quality Engineering & System Assurance Sciences Group at RDECOM-ARDEC at Picatinny, New Jersey.  She is responsible for measurement and analysis, risk management, estimation, and decision analysis technology development and application across a wide base of DoD, Government, and Commercial programs and organizations.  Her responsibilities encompass technology development, integrated process definition, and practical technology application to support a variety of Performance and Decision Analysis requirements across numerous technical, acquisition, and management domains at multiple organizational levels. Ms. Jones is the technical lead and project manager of Practical Software and Systems Measurement. This project is an international technical initiative responsible for the development and transition of effective measurement practices into the software and systems development communities.  Ms Jones is a primary author of Practical Software Measurement: Objective Information for Decision Makers.  She is responsible for directing the transition of PSM and related measurement guidance into practice across a wide community of users through DoD, government, and industry.  She has been instrumental in linking corporate measurement processes to validated improvements in project and organizational performance. Ms. Jones is a technical expert to the US Technical Advisory Group to International Standards Organization SC7, System and Software Engineering.  Ms. Jones is the convener of Special Working Group 5, Standards Management.  Ms. Jones is co-editor of ISO/IEC/IEEE 29148, Requirements Engineering. She previously was co-editor for ISO/IEC/IEEE 15288:2008, System Life Cycle Processes, editor of the revision to ISO/IEC 15939:2007, Software Measurement, and ISO/IEC/IEEE 16085:2006, Risk Management.  Ms. Jones is also co-editor of ISO/IEC 15288, System Life Cycle Processes and ISO/IEC/IEEE 29148, Requirements Engineering. Ms. Jones holds a B.S. degree in Computer Science/Mathematics from the University of Georgia and an MBA in Management Information Systems from the University of Rhode Island. Contact information: Email:  cheryl.jones5@us.army.mil Website:     http://www.psmsc.com The essay examines optimism.  When is optimism a good thing and when is it a bad thing? Perhaps the right answer is optimistic realism. Contact information for the Software Process and Measurement Cast Email:  spamcastinfo@gmail.com Voicemail:  +1-206-888-6111 Website: www.spamcast.net Twitter: www.twitter.com/tcagley Facebook:  http://bit.ly/16fBWV The SPaMCAST's production schedule is on the Software Process and Measurement Facebook page.  Yell at me if you have ideas for future interviews or essays.  Your thoughts, comments, suggestions, and ideas are welcome. Conferences and Speaking Engagements in 2010 (To Date)   Quest Conference in Dallas April 21 - 23.  I will be talking on "Process Improvement in a Multi-Model World".  The conference includes two days of workshops.  The website to get more information is http://www.qaiquest.org/dallas/index.html Next! The interview in the SPaMCAST 83 is with Gary Gack.  We discussed his new book, “Managing the Black Hole”. The book explores customer engagement, metrics, planning and monitoring projects.

Listen to Richard Crisp, Director of Requirements and Quality Management Product delivery, as he shares his experience of how requirements engineering can help unify product development teams so that together they can deliver a high-quality product that meets the needs of the customer, on time and on budget.

Lecture 13: Requirements Engineering

Lecture 13: Requirements Engineering

Listen to Patrick Roach, Principle Engineer for an Aerospace and Defense Organization, talk about the importance of requirements engineering within his industry and how he's found that improving requirements practices is essential to project success.

Graham Stradling at Alcatel-Lucent talks about the importance of effective requirements management in delivering high quality systems to customers. With technologies converging and increased pressure on the telelcommunications industry to provide increased speed and bandwidth to customers, ensuring a reliable, fast efficient system is critical in order to maintain a competitive edge. By managing requirements across the whole lifecycle, Alcatel-Lucent are able to make sure that quality is not compromised and they can successfully meet their customers' needs.

In this episode we talk to Christof Ebert about requirements engineering. As the name "engineering" suggests, we need to be systematic when working and managing requirements. Christof will structure RE into several activities, namely elicitation (identifying the relevant requirements), specification (clearly describing requirements), analysis (synthesizing a solution), verification and validation (achieving good requirements quality), comittment (allocating requirements to a project, product release or iteration), and management (keeping track of the implementation status of requirements). In this episode we discuss these activities and highlight lots of practical guidance.

In this episode we talk to Christof Ebert about requirements engineering. As the name "engineering" suggests, we need to be systematic when working and managing requirements. Christof will structure RE into several activities, namely elicitation (identifying the relevant requirements), specification (clearly describing requirements), analysis (synthesizing a solution), verification and validation (achieving good requirements quality), comittment (allocating requirements to a project, product release or iteration), and management (keeping track of the implementation status of requirements). In this episode we discuss these activities and highlight lots of practical guidance.

In this episode we talk to Christof Ebert about requirements engineering. As the name "engineering" suggests, we need to be systematic when working and managing requirements. Christof will structure RE into several activities, namely elicitation (identifying the relevant requirements), specification (clearly describing requirements), analysis (synthesizing a solution), verification and validation (achieving good requirements quality), comittment (allocating requirements to a project, product release or iteration), and management (keeping track of the implementation status of requirements). In this episode we discuss these activities and highlight lots of practical guidance.

Requirements Engineering - lecture, Petri Lillberg

Requirements Engineering - lecture, Marjo Kauppinen

Requirements Engineering & Analysis Design - lecture slides