Aufwandschätzungen mit Story Points bzw. Stunden oder doch eher 'No Estimates'? - agilist. Quelle: Generell gilt: je mehr Möglichkeiten man hat, desto schwieriger kann es sein, sich für die Richtige zu entscheiden.
Bei Aufwandschätzungen ging es mir ähnlich. Mit der Einführung von Scrum war Planning Poker mit Story Points das Mass aller Dinge. Mit der Zeit realisierten meine Teamkollegen und ich jedoch, dass es durchaus auch Konstellationen gibt, in denen wir die Schätzung nach Stunden bevorzugten. In der Folge kam es auch vor, dass wir Planning Poker mit Stunden durchführten, ebenfalls mit der für Planning Poker vorgesehenen Fibonacci-Zahlenfolge. Soweit, so gut. Wann machen welche Schätzmethoden am meisten Sinn und bei welchen Konstellationen können wir Schätzungen mit gutem Gewissen ganz weglassen? In der untenstehenden Tabelle haben wir einige positive und negative Aspekte für die erwähnten Schätz-Varianten aufglistet. Zwei Alternativen zu den in der Tabelle behandelten Schätz-Varianten T-Shirt-Grössen: z.B. Einige abschliessende Erkenntnisse Fazit. 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. Old Muscle Memory. 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. Set the Stage When I run this exercise, I begin with some conceptual groundwork. I first draw a diagram of three concentric circles and explain that each one of us steps in and out of those zones as we interact as a team: 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. Here, I will continue that voyage by exploring ownership. High Performance Defined. 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. 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. Agilität braucht Führung.
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. 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. 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. How to Kick-off Your Agile Transition with Scrum Team #1. User Stories beschreiben Anforderungen statt Bedürfnisse... - agilist. Wie im letzen Blog Post dargestellt, ist das Template der User Story scheinbar relativ simpel: “Als User möchte ich mich einloggen, damit ich mich einloggen kann.”
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? Scrum or Kanban, that is the question that keeps coming up!
But is it really an either/or question? Some people would have you choose. I believe they are complementary approaches and a pragmatic approach is to use each when appropriate. Tools for Distributed Agile Teams. We prefer face-to-face interactions, but distributed teams don’t have that luxury. Fortunately, tools exist to help your agile team. Editors’ note: This article was written by Lynn Winterboer and Katrina Starkweather. We have worked together since 1996 and been friends since 1994. Managing Requirements Dependencies Between Agile and Lean Teams. Sometimes functional dependencies occur between requirements that are being implemented by different teams. For example, requirement X depends on requirement Y and X is being worked on by team A and Y is being worked on by team B.
Agile Software Development and CapEx/OpEx. 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. Insurance is great for all sorts of things. I have health insurance in case I become ill or injured. I have auto insurance that will repair or replace my vehicle if it's damaged. Upfront Thinking Is Like Insurance. Insurance is great for all sorts of things. Budget When You Can’t Estimate. I've written before that we should only estimate if having the estimate will change someone's actions. Normally, this means that the team should estimate work only if having the estimate will either: enable the product owner to better prioritize the product backlog, or let the product owner answer questions about when some amount of functionality can be available.
But, even if we only ask for estimates at these times, there will be some work that the team finds extremely hard or nearly impossible to 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.