8 ms·
At Pivotal, I learned that having sprints is silly. They have the concept of one week iterations instead. The PM just keeps a rolling backlog of stories and dev
by latchkey 7y ago
At Pivotal, I learned that having sprints is silly. They have the concept of one week iterations instead. The PM just keeps a rolling backlog of stories and devs just pick the next one off the top. Dev's are responsible for pointing the stories and the sum of those points averaged over time (usually 2-3 weeks) become velocity.
Just keep the velocity as consistent as possible and things work out for the best. If the PM wants a story moved up the list, then they can see how much work will fit into an iteration and how it will affect schedules.
All of this is managed in their homegrown, but publicly available tool called Pivotal Tracker. You can read the website documentation for a more thorough explanation. Once I learned this methodology and started practicing it like a religion, deadlines went away and PM's could estimate due dates many weeks in advance. It was a life changing experience that I highly recommend at least giving a shot at your own workplace.
- alasdair_ 7y agoThis sounds exactly like every other sprint-based process I have ever encountered.
- latchkey 7y agoSprints have deadlines and a set amount of work... 'A two week sprint.' Iterations are 1 week and there is no expectation that a story will always fit within the current iteration. The only tool that I have found which can accurately visualize this difference is PT.
- supermatt 7y agoWhat is the point in an iteration?
- latchkey 7y agoGood question. An iteration is a marker to generate velocity. All of the points collected in that week are summed together and the average of those points across a configurable threshold (typically 3 weeks) is the velocity. Once you have a velocity, you can start to make predictions about the future. For example, if velocity is 10, that means 10 points worth of stories can fit into an iteration. If the PM moves another story into the iteration, the last story would be automatically pushed into the next iteration. Makes it easier to answer the question of 'when will a story be done?' as well as 'how will changing the flow of stories affect deliverables?' Highly recommend you read the documentation, it has been formed over many years and is excellent. https://www.pivotaltracker.com/help/articles/quick_start/ https://www.pivotaltracker.com/help/articles/quick_start/
- winrid 7y agoBecause then we'd call them weeks and Sprints would be Fortnights :) In all seriousness I'm curious about the story pointing. Does the team meet together for that at Pivotal?
- latchkey 7y agoRepeated from above: Pivotal has 3 regular meetings: daily morning standup (short), iteration planning (monday), retrospective (friday). Any new stories during the week that haven't been pointed get pointed in the morning meeting.
- vidarh 7y agoIn practice, most places I've worked treats sprints much closer to how you describe your iterations than to a fixed amount of work. Most of the time, the sprint planning just provides some ceremony around ensuring important stories are discussed and points allocated, and priorities set, and the planned sprint is pretty much a line in the backlog that suggests an aspirational goal that is likely to change. The point is rarely to hit exactly that, but for it to serve as a means of talking about what needs to be done first - whether something needs to fit into this round, or can wait for the next. It also serves as a means of talking about inter-dependencies and sequencing of changes.
- latchkey 7y agoI think you've been lucky in where you have worked. You read some of the other responses and it isn't the case at all. I've seen some really tragic examples. Pivotal has 3 regular meetings: daily morning standup (short), iteration planning (monday), retrospective (friday). Any new stories during the week that haven't been pointed get pointed in the morning meeting.
- 0xFACEFEED 7y agoout of curiosity what value do you see in morning standups? 15 yrs and i still don't see it (i've really tried).
- latchkey 7y agoI agree that the whole typical 'what did you do yesterday' is indeed lacking value. The standups are mostly just pointing the stories that need pointing, covering any questions and picking the pairs for the days work (pivotal is 100% pair programming). The meetings can be done within 5-15 minutes at most. I'm currently living at a yoga retreat center in the mountains of Vietnam. I can see from the practice that the first few minutes of silence is good to clear the mind. I think having standups is a similar good way to start the day with a positive attitude.
- 7y ago
- matt74827289 7y agoThe end of the sprint should not be a deadline, but a goal. Wasn't that kinda the point of the article? No one ever said a story has to fit within a sprint, that's not how agile or sprints are supposed to work. Some stories take multiple sprints. You should always break down large stories into sub-tasks that do fit within sprints. This iteration thing your describing sounds almost exactly like sprints to me, just reworded to sound like their own thing.
- latchkey 7y agoAh, the difference is that with iterations, there is never an 'end' and goals are just epics. Correct, all larger stories should be broken down. To be super clear, this is not my own thing. =) It is Pivotal's thing. I am just explaining the process as it was taught to me.
- alasdair_ 7y ago>Ah, the difference is that with iterations, there is never an 'end' and goals are just epics. Jira uses epics in the same way. And I'm not sure what you mean by "there is never an 'end'" - how does that differ from sprints? Iterations and sprints are just two words for exactly the same thing.
- kerblang 7y agoWhen you say, "devs just pick the next one off the top", that sounds very much like Kanban instead of Scrum. Kanban is radically different but considered "agile". When Scrum degenerates into mgmt screaming, "you missed all your deadlines - again!", Kanban is often a great source of relief, because the only deadlines that count anymore are the "real" ones. It also allows much more flexibility with shifting priorities, which stakeholders love. Absolutely worth a try when Scrum has become a tool of oppression & misery.
- latchkey 7y agoI wouldn't really try to put a name on it other than Pivotal Process or Pivotal Methodology... I was just googling around to see if they even name it and found these articles... https://infocus.dellemc.com/rahul_bhandari/software-development-dell-agile-methodology-pivotal/ https://infocus.dellemc.com/rahul_bhandari/software-developm... (corporate version) https://pivotal.io/agile https://pivotal.io/agile (this one bugs me a bit since it really just compares against waterfall) https://medium.com/@ryanjjones10/what-is-the-pivotal-process-417fab075f4f https://medium.com/@ryanjjones10/what-is-the-pivotal-process... (this one is more accurate)
- kerblang 7y agoOkay well it looks like they've put even more emphasis on pair programming, which Kanban certainly doesn't require, and... I'm not gonna advocate for that part.
- alasdair_ 7y agoPair programming all the time comes from XP. Almost no one does it, not even Kent Beck. In fact, the only place that I know of that tried "real" eXtreme Programming was the Chrysler Compensation project, which ultimately failed. I'd be amazed that Pivotal actually does pair programming all the time, except that they are in the business of selling tools to facilitate exactly this process.
- 7y ago
- balfirevic 7y ago> Sprints have deadlines and a set amount of work... Well, they shouldn't: https://www.scrum.org/resources/commitment-vs-forecast https://www.scrum.org/resources/commitment-vs-forecast
- nradov 7y agoYou don't understand how agile development actually works and appear to be confused about terminology. There is no difference between a sprint and an iteration; they are two words for the same thing. A sprint is a planning cycle, not a deadline. Many other tools such as Jira or Rally work as well or better than PT. Recommend you broaden your experience.
- mattlondon 7y agoSounds like every agile team I've ever worked on - sprint and iteration is usually interchangeable. The problem is that Devs making estimates tends not to be accurate IME. Some stuff is easy to estimate, but adding in new & significant functionality is notoriously usually hideously mis-estimated (either high or low). So much so that the numbers basically b come meaningless and can't be relied upon because every major new thing was a lot easier/a lot harder than expected. The reaction to this is to split the task up, but this often requires that you do a lot of pre-work-work to architect and design the work so you know how it can be broken up, and that design work needs to be estimated so you are back at square one with wildly inaccurate estimates.
- latchkey 7y agoIf the story estimation isn't accurate, then the velocity goes haywire and this shows up in the reporting in Pivotal Tracker. So like you said, devs learn to get better at forcing the PM's to split the stories into smaller chunks. Smaller stories are almost always easier to accurately point since it is always 2 (1 point for the story, 1 point for testing). The numbers are not meaningless though. That is why velocity is an average of 3 weeks. A single week doesn't blow things out of the water and if it is a new project, the expectation is that we won't know where we are at all those first 3 weeks. It gives a built in ramp-up period for the project. Agreed, the PM's role is SUPER important. For this reason, at Pivotal the PM's usually have a developer background.
- ec109685 7y agoAren’t you putting all your faith in the PM in this methodology? The way you describe it, a developer’s role is to point out stories and jointly perform the work the PM has allocated. Instead, if those same developers understood the users, use cases and metrics and co-created the work the team does, the team would have 10 or mor engaged minds all working to make a better experience instead of the one super PM.
- latchkey 7y agoIt isn't black and white like that. The team always has a voice and can express it at any time. Communication is always key and that is the whole point of developers pointing stories. They could just call a story 8 points and the PM would never get it into the backlog. =)
- mikekchar 7y agoIn my experience, there are a few reasons why you would choose sprints over a continuous backlog like this. Originally, these kinds of agile processes did not use continuous deployment. Often you used trunk based development (TBD) where you merged your work directly into trunk/master several times a day. Continuous Integration servers were invented because this style of CI often broke the build. You wanted the test suite to run after you pushed so that other developers would be alerted to a broken build before they pulled. Of course even better to check before you merge, but the source management systems of the day often weren't capable of doing that easily. Sometimes even making a branch was hard work. The end result of this kind of system was that master was not always deployable. You needed a point in time where the system was deployable. That's the end of the sprint. Although it's a very unusual way of doing development these days, prioritising true CI over CD has definite advantages in some environments. In the same spirit, the longer you keep code out of trunk/master, the more risk you have and the more difficult it is for people to do refactoring. If you make large changes over a whole week, then you end up with difficult integrations. Even if you aren't doing true CI (i.e. actually integrating your code with everyone else's on a continuous basis), it's important to limit the amount of time your branch is held out of master. If you have a 2 week sprint and you have 1 week stories, you will almost certainly fail every single sprint (been there, done that ;-) ). The only way for a sprint to succeed is if the vast majority of stories are small enough that you are unlikely to start it without finishing it. The funny thing about having small stories (around 10% of the size of your sprint) is that if you are doing them, then having a sprint end is inconsequential. You may drop a story or two from your board if things don't go as planned, but you will almost never start something and not finish it (especially if you prioritise stories by risk). So the main reason for preferring sprintless backlogs is because keeping the story size small is difficult. In order to keep all your story sizes small, you have to be doing some things very, very well. First, you need to be doing your analysis very well. If you don't know exactly what you are building before you start, you will have wide variability in the amount of time it takes. It will also be very difficult to break problems apart because you aren't entirely sure where the good break points are. Second, your code needs to be very, very clean. You need to be refactoring literally constantly. The code needs to be simple in order to break your problem up easily. This requires a lot of iterations of design in all of your code as the code grows. All of this actually feeds back to the preference for CI over CD. It's not a system that a lot of teams will prefer to use, but it has definite advantages. My experience has been that the potential is quite a bit better, especially over time. You need a team that is completely on board, though. It is especially difficult for PMs who usually don't want to think about problems in as much detail as is necessary for this system to succeed. However, I would encourage developers to keep an open mind because when it works, it works amazingly well.
- meerita 7y agoHi, PM here. I ditched scrum long time ago with the team and setup 1 week cycles. We meet on monday, to kick off and see results at friday. We managed to keep executable development cycles, so from my part, i tend to ask for less every single weekend because that's how I get most of the results, and keep moving. In the end, it's better than seeing results every 2 weeks and some major results in a month or so. I preffer to move quickly, and iterate those "mini-sprints" in case one went wrong.
- latchkey 7y agothis ^^^^^
- KZeillmann 7y agoThis sounds like Scrum with one week sprints.
- meerita 7y agowe don't do retrospectives, groomings, estimation of stories, etc.
- thomk 7y agoThis actually sounds a lot like Kanban.
- himynameisdom 7y agoThis sounds a lot like Kanban for Scrum Teams. https://www.scrum.org/resources/kanban-guide-scrum-teams https://www.scrum.org/resources/kanban-guide-scrum-teams
- tootie 7y agoIt strongly depends on the maturity of the team. All the comments in this thread are assuming the point of view of the heroic developer and his tribulations. Managers know that some devs will sit on their hands and do shoddy work without constant prodding. A good process has the appropriate amount of incentives to move quickly and checkpoints for quality and accuracy. The more mature your team, the lighter these checkpoints can be. I've found that a lot of teams will essentially graduate from sprint-based Scrum to Kanban once they've acclimated and gained some trust. Same with estimates. They may be necessary at first, but eventually become less valuable.
- slumdev 7y ago> At Pivotal, I learned that having sprints is silly. They have the concept of one week iterations instead. So you're doing Scrum with a 1-week sprint?