Definition of Done vs. User Stories vs. Acceptance Criteria. Definition of Done vs. User Stories vs. Acceptance Criteria. Agiler Vertrieb und Agile Sales - Agile Unternehmen. Innerhalb der Softwareentwicklung ist Agilität weit verbreitet.
Doch wie lässt sich der Begriff “Agilität”, den man betriebswirtschaftlich auch mit Flexibilität beschreibt, auf den Vertrieb übertragen? Schauen wir uns doch erst einmal die Definition des Vertriebs an. Das Gabler Wirtschaftslexikon sagt dazu: “Vertrieb beinhaltet v.a. den Verkauf von Waren; Warenverteilung (Logistik, Marketinglogistik), Steuerung der Außendienstorganisation und Pflege der Beziehungen eines Herstellers zum Handel bzw. beim Direktvertrieb (direkter Vertrieb) zum Endkunden. Neuere Ansätze betonen die hohe Bedeutung des Kundenmanagements im Rahmen des Vertriebs. Nun ist jedoch festzuhalten, dass Vertriebsabteilungen in Unternehmen den Fokus oft auf Bestandskunden setzen, ohne dabei die Flexibilität besitzen, auch neue Projekte und Ideen innerhalb der Abteilung anzugehen.
A day (or a sprint) in the life of a BDD team - John Ferguson Smart. Later during the sprint, the team members who will be working on a particular feature or story get together to discuss the detailed requirements.
This typically involves in the least a business representative (BA), a developer and a tester. The goal of these “three-amigo” sessions is for the team members to get a deep shared understanding of the business rules and acceptance criteria for the story, and to actively uncover any previously-missed complexity or risk that might trip up subsequent development efforts. Teams often express acceptance criteria using the well-known “Given-When-Then” format, like in the following example: Scenario: Applying for a joint credit card with insufficient combined income Combined income must be over £10,000 Given Susan has an income of £3000 And Jim has an income of £2500 When Susan and Jim apply for a joint credit card online Then the application should be refused.
Agile Data Warehousing With The Data Vault – Part 1 – Data Vault and DV 2.0 Education & Training. The Agile Manifesto has 4 core mandates and 12 principles.
Before you go jumping the gun and accusing them of being brash, remember they DO value items on the right, however – They value items on the left MORE! The 4 core mandates include: Aufwandschätzungen mit Story Points bzw. Stunden oder doch eher 'No Estimates'? - agilist. Measuring the Progress of Agile. The eleventh State of Agile survey has just been published by VersionOne.
These reports are invaluable in helping agile practitioners understand where their practices, problems and challenges fit the context of the wider world. As with all VersionOne’s previous reports, the eleventh survey paints a picture of the onward march of agile. Its progress is rarely in a straight line, however, and this latest survey has revealed a very interesting contradiction. Increased Focus on Business Value? When respondents were asked how the success of agile initiatives were measured, the second ranked answer after “on-time delivery” was “business value.” When, in the same survey, participants were asked how the success of agile projects (as opposed to initiatives) are being measured, the percentage who answered “business value” fell by half. The Fear and Vulnerability Retrospective. What makes your teammates lose sleep at night?
The best way to find out is simple, but not always easy: ask them! In this post, I’ll be presenting a technique--suitable for a retrospective or a lift off--that opens up channels of communication about the topics of fear and vulnerability. Leadership & Effective Decision Making on High Performance Teams. Trust, Vision and Ownership In a previous post, I identified "3 Necessary Conditions for 'Going Agile'": Trust, ownership and vision.
There, I used up my quota of blog space by focusing on trust and its impact on a high-performance team. The Role of a Product Owner (Part 3): Anti-Patterns. Part one of this series examined the responsibilities and characteristics of a product owner; part two looked at their daily activities during a sprint.
This third post focuses upon common anti-patterns seen with the product owner role. Here are my “dirty-dozen” product owner anti-patterns: 1. No Single Product Owner Each Scrum team must have a single product owner. Solution: Identify a single product owner for each team. 2. The product owner must be available to the team to answer questions whenever required so as not to reduce capability and lower morale. Solution: The product owner must be present to support the team during development - aim for at least 50 percent availability. 3. When the real product owner is unavailable, and a proxy is appointed, then it is critical that they are fully empowered within the role. Solution: Engage the real product owner or fully empower a proxy. 4. There are only three roles within a Scrum team - product owner, Scrum Master and developer. 5. 6. 7. 8.
Agile Data Warehousing and Business Intelligence in Action. Very often the construction of a Data Warehousing / Business Intelligence (DW / BI) system is performed following the flow of traditional engineering: analysis, design, construction, testing and implementation.
Communication between developers and people interested in the business is almost nonexistent, and developers are interested in technologies for working with data but often neglect to ask this most important question: "What business questions do we want to answer with the available data in order to support the decision-making process? " In this article, I will discuss how to build DW / BI systems following many of the practices and agile principles mentioned in the book of Ken Collier: Agile Analytics: A Value-Driven Approach to Business Intelligence and Data Warehousing. Data Warehousing / Business Intelligence (DW / BI) system A system has inputs, processes and outputs. Considering this approach, the inputs are all sources from which we need to extract data. Agile Manifesto Values add on for large enterprises.
The Agile Manifesto was written in 2001 by a group of software thought leaders.
It articulates a common set of beliefs based on empirical evidence of a better way of delivering software to add business value. One of it’s strengths is that it is articulating a mindset in the form of Values and Principles, which guide context specific decisions and practices. Still relevant today It has stood the test of time remarkably well. In particular for large enterprises, it is just as relevant today as it was in 2001. Autonomie und Orientierung. Accountability on a Agile Software Development in the Presence of Governance. Scrum, Kanban, Scrumban – a fast overview and rough categorization when to use what method – OnTheAgilePath.
Untitled. An Introduction to Modern Agile. Agile is modernizing.
Thanks to Lean and Agile pioneers and practitioners, we now have simpler, safer, speedier ways to achieve awesome results. We call these new approaches “Modern Agile” because they’ve evolved far beyond early Agile methods. An Introduction to Modern Agile. Independent Testing and Agile Teams. The majority of testing, and in simple situations all of it, is performed by an agile delivery team itself. This is because we strive to have cross-functional “whole teams” that have the capability and accountability to perform the activities of solution delivery from beginning to end. For organizations new to agile this means that you embed testers on agile teams and for organizations experienced in agile that you’ve managed to motivate agile team members to gain testing skills over time (often via close collaboration with other people who already have those skills). This blog is organized into the follow topics: Parallel Independent Testing The whole team approach to development where agile teams test to the best of the ability is a great start, but it isn’t sufficient in some scaling situations.
Figure 1. Investigative/exploratory testing. Why Independent Testing? There are several reasons why you should consider independent testing: Regulatory compliance. 12 Habits that Will Make You an Excellent Team Lead. The Team Lead Role in an organization that is performing Software Development using DAD is the most influential role and the role can be both challenging and fun.
You do not need to be a technical expert to be a very effective Team Lead however like most professions having a strong technical background will definitely help you to connect better with the Team Members. Here are 12 Habits from veteran Scrummasters applying Scrum. 10 Proven Stakeholder Communication Tactics During An Agile Transition.
Stakeholder communication: It is simply not enough for an agile product development organization to create great code and ship the resulting product like a clockwork. You also need to talk about, particularly in the beginning of your agile transition. Marketing the agile journey of product and engineering to the rest of the organization—and thus getting their buy-in—is a critical success factor to step up the game: You want to become agile, not doing “Agile”. So, learn more about ten proven stakeholder communications tactics that contribute to making this happen. Stakeholder Communication Channels During an Agile Transition Do good and talk about it—a simple necessity, particularly if your agile transition is supposed to be embraced by the whole organization over time.
How to Kick-off Your Agile Transition with Scrum Team #1. Agile Transition—TL;DR A hands-on, practical guide on how to kick-off an agile transition: Embrace the agile mindset and scale your engineering and product organization to harvest your organization’s full potential. The Big Picture of an Agile Transition at a Fast-Growing Startup. User Stories beschreiben Anforderungen statt Bedürfnisse... - agilist. Agile Excel Spreadsheet for the Product Backlog. I want to show a real easy way to put user stories in a spreadsheet-based product backlog. I wrote this after seeing someone tweet a screen capture of a product backlog I made nine years ago and thought to myself, “Yikes, that's out of date for how I do it today …” So in this post, well look at an agile product backlog template in Excel.
As you probably know, I'm a big fan of writing the product backlog in the form of user stories and of writing user stories in the form: “As a _____, I ______, so that _______.” An example being: “As a frequent flyer, I really want to be able to connect to the internet while flying so that I can update my blog while traveling rather than having to save this as a text file and updating my blog later.” (Can you guess where I am while writing this?) Forbes Welcome. Agile Data Warehousing and Business Intelligence in Action. Road-mapping Your Way to Agile Fluency. One of the things we are often asked to do at ThoughtWorks is help organizations and teams transition to new ways of working and thinking about work.
Frequently, these requests are driven by an organization’s desire to compete more effectively in their marketplace, or to protect themselves against disruptive newcomers. Often beginning with the Information Technology (IT) function or department, they have specific goals in mind, such as adopting Continuous Delivery or transitioning to a DevOps culture. Sometimes, IT has made a start and has one or two (or several) teams using agile approaches, but have now realized they need to bring their business partners along on the journey. Transitions of any kind usually imply a long and nebulous journey, so it’s unsurprising that before too long, questions come up around how teams can best measure their progress. These are not unreasonable questions, and a large number of different tools and maturity models claim to help find the answer.
Context. Scrum Breakfast: What's the difference Scrum or Kanban? Tools for Distributed Agile Teams. We prefer face-to-face interactions, but distributed teams don’t have that luxury. Managing Requirements Dependencies Between Agile and Lean Teams. Agile Software Development and CapEx/OpEx. An important financial governance concern in modern enterprises is how to expense costs properly. This of course includes the costs of IT, including the costs associated with agile software development teams.
Business Value of Agile Data Warehousing User Stories. Advice on How to Split Reporting User Stories. Agile Estimating and Planning. Agility Requires Safety. Upfront Thinking Is Like Insurance. Upfront Thinking Is Like Insurance. Budget When You Can’t Estimate. Not Everything Needs to Be a User Story: Using FDD Features. How Full to Fill a Sprint. The Agile Rhythm: How to Find Yours & Why. Priority Poker Order. The TAGRI (They Ain't Gonna Read It) Principle of Software Development. Agile Frameworks: Does Anyone Know What A Framework Is? – The Cutter Blog. User stories are not requirements.
Scaled Agile Framework – SAFe for Lean Software and System Engineering. Your Agile Project Needs a Budget, Not an Estimate. Start, Stop, Continue, More of, Less of Wheel - Agile Retrospective Resource Wiki. Agile Retrospective Resource Wiki - Agile Retrospective Resource Wiki. HERMES. Using Scrum & Kanban & SAFe & DSDM (& DAD)
Scrum Data Warehouse Project. Disciplined Agile. Communication and Agile Modeling - Lynn Winterboer Agile Training & Consulting. DSDM Atern. Modern Agile - Industrial Logic. Manifesto for Half-Arsed Agile Software Development. Versprechen, aber richtig. Ich verspreche! Promises, Promises (2014) The Main Benefit of Story Points. How Visual Systems Make It Easier to Track Knowledge Work.
Scaling Agile Data Warehousing with the Scaled Agile Framework (SAFe) One Organisational Backlog? Or Two? Data Warehouse Agility Array Conference2011. Microsoft Designs Team Foundation Server 2015 for Agile, DevOps, ALM. Agile Engineering Stages. Content Access. Are Agile and CMMI compatible? Say goodbye to the old to-do list: kanban is the easiest way to organize projects. Forrester. Got Technical Debt? » Technical Debt. Your Path through Agile Fluency. The Agile Maturity Model (AMM) Atlassian Cloud. The Cultural Impedance Mismatch Between Data Professionals and Application Developers. 7 Obstacles to Enterprise Agility. Modelstorming.com. Outracing BI avalanches - an agile BI success story - diginomica. Memorandum: TDWI - The Data Warehousing Institute. Coaching, Training, & Consulting for Agile Software Organizations. Complexity, Volatility, and Severability of Requirements Determines Agile Applicability.
Just enough architecture. Archiv - Detailansicht: TDWI - The Data Warehousing Institute. Pragmatic solutions gmbh – agile coaching & training.