Secure Software Development. I’ve been a fan of Agile methodologies for quite some time now.
As an Agilist, I would scoff at the Waterfall process I was taught during my studies. I did read a couple of times that the original paper introducing the Waterfall model wasn’t really supportive of it at all, but I’d never read that paper myself. Until now. Here’s what I found what its author, Dr. Winston Royce, has to say. Attitude The heart of software development is analysis and coding, “since both steps involve genuinely creative work which directly contributes to the usefulness of the final product.”
Scrumpatternssummary - www. Aggregate Velocity - Published Patterns. Aggregate Velocity... your product has grown to multiple teams, each one of which was drawn from the single, original team whose velocity had stabilized.
The Product Owner wants to establish a new velocity for the Product Backlog. You need to know the development velocity to establish release schedules and to estimate delivery ranges for PBIs. In a single-team Scrum you can use that team's velocity, but what do you do in a multi-team Scrum? Each team has its own velocity, and these velocities cannot trivially be averaged or normalized with each other. Just as there is a gestalt effect between team members that contributes to the high velocity of a team, so there are non-linear influences between multiple coordinated teams that can either increase or decrease their collective effectiveness. During sprint planning, team members collectively estimate on the product backlog based on their intuition and past experience as a team. Assume that each PBI is estimated by only a single team. Five Tips for Impediment Resolution with Scrum. Impediments can slow down or even halt the progress of an otherwise well-functioning Scrum team.
Let's take a look at the most common challenges that crop up on teams and what steps you can take to resolve them. Problems: The Agile Inception Deck « The Agile Warrior. Download Blank Inception Deck (pptx).
One area most agile methods are completely silent on is project chartering. Below is a lightweight you can use to fill this gap and get your project headed in the right direction long before the first line of code every gets written. 10 questions to ask at the start of your next project. ScrumReferenceCard.pdf. Why use Tasks? « Agile Development Presentation | Main | Porters!
Presort! » June 08, 2007 Why use Tasks? As we coach software development teams in Kansas City, we are often asked about the process of breaking User Stories down into development tasks (anything related to implementing and verify a User Story). 1) Iteration Planning Tasks are a good last check for iteration planning purposes. During planning, openly discussing development tasks gives all team members a view of what will take place while implementing the stories selected for the iteration. Agile estimation – story points vs. hours « epistemologic. Once again, discussions at work have driven me to write this.
This time, the topic of debate (or rather, amusement) is that in an agile team, hours (or days) and not story points are a better way to estimate user stories. I disagree. Developers are, in general, more aware of the potential complexities that they can run into in the process of implementing a story. Despite this cognizance, it is often hard to predict exactly what these complexities might be. Obviously, if a developer knew the exact nature of the issues that he will run into, he can account for those and predict exactly how much time the work might take. Further, depending on the specific process being used in a given team, it is possible that the developer(s) who estimated a given story is not the one who ends up actually doing the implementation.
Picking Agile vs. Waterfall “Projects”: a Ten Point Quiz. Posted on March 4, 2011 by Dean Leffingwell in Enterprise Rollout For some reason, I woke up today realizing that I have been working with, and writing exclusively about, enterprise scale software agility full time now for five years running.
Agile Product Ownership in a nutshell. This is basically a 1 day product ownership course compressed into a 15 minute animated presentation.
There’s obviously more to product ownership than this, so see this is a high level summary. Here’s the complete drawing (.png format)Here’s a downloadable version of the video, in case you don’t want to stream (.mov format, 90 Mb) Special thanks to Alistair Cockburn, Tom & Mary Poppendieck, Jeff Patton, Ron Jeffries, Jeff Sutherland, and Michael Dubakov for providing many of the models, metaphors, and ideas that I use in this presentation. Henrik Kniberg. I debug, refactor, and optimize IT companies.
And jam alot too. Friendly Guide to Climate Change (and what you can do about it) I’ve spent ALOT of time the past few months trying to understand climate change and global warming, and how to effectively contribute. I’ve dug through 1000-page scientific reports, talked to experts, and basically tried to digest as much information as possible. I was surprised by how little I knew before. So here’s a short animated video summarizing the whole issue. Please help spread it as widely as possible! 10 Things to Drive Your ScrumMaster Crazy. Game « Agile Belgium. Scrum Simulation with LEGO. Wp-content/uploads/2011/12/Scrum-Simulation-with-LEGO-Bricks-v2.0.pdf. Play the Scrum Simulation (based on XPGame) for Great Learning.