tag:blogger.com,1999:blog-5028009537158799436.post2292226244504567498..comments2023-07-10T04:50:03.236-07:00Comments on Building Real Software: Hardening Sprints. What are they? Do you need them?Jim Birdhttp://www.blogger.com/profile/17371102366836131341noreply@blogger.comBlogger8125tag:blogger.com,1999:blog-5028009537158799436.post-21220728854792285662016-02-01T11:08:58.571-08:002016-02-01T11:08:58.571-08:00I agree with the Hardening sprint and it really is...I agree with the Hardening sprint and it really is very dependent on the complexity of the product, where the final RC build is validated along with other artifacts, like licensing and covers a end to end testing from downloading to activation. A challenge which we face is in case of encryption changes the export compliance approval is time consuming and getting that clearance take more time than to release in production. That is a legal requirement. Looking forward for suggestions.Susmitanoreply@blogger.comtag:blogger.com,1999:blog-5028009537158799436.post-49288008596266523032014-12-22T21:32:01.472-08:002014-12-22T21:32:01.472-08:00I think it should be used only in the scrum of scr...I think it should be used only in the scrum of scrum scenario, though I have seen a situation where as a vendor we were developing webservices and customers in house team was working on UI. However this team had most of the individuals on contract and therefore it was not possible to have them available throughout the release. Workaround was to have them work on the webservices after certain functionality is available. In this situation it was necessary to have iteration H. Any other suggestions would be welcome.Prashanthttps://www.blogger.com/profile/12608886512514734509noreply@blogger.comtag:blogger.com,1999:blog-5028009537158799436.post-41662905679288940762014-11-10T13:01:11.399-08:002014-11-10T13:01:11.399-08:00¡Excellent article! Perhaps as the agile developme...¡Excellent article! Perhaps as the agile development team matures, it starts moving towards Devops -which can also help defuse the dangers of hazardous release sprints...Alejandro Teruelnoreply@blogger.comtag:blogger.com,1999:blog-5028009537158799436.post-66453784720020506662014-02-20T23:15:08.294-08:002014-02-20T23:15:08.294-08:00Highly detailed and a useful article!
I find peop...Highly detailed and a useful article!<br /><br />I find people who are Anal about NOT using Hardening (no pun) sprints either -<br />(a) Have never successfully delivered software themselves, or <br />(b) Are so far up there with the whole Agility elitism that they fail to understand that in the end - it's not about creating quality processes but delivering quality product and business value to PO and end-users.RJnoreply@blogger.comtag:blogger.com,1999:blog-5028009537158799436.post-82850376032504006502014-01-20T20:54:14.714-08:002014-01-20T20:54:14.714-08:00Jim,
Love the article. I agree that a hardening Sp...Jim,<br />Love the article. I agree that a hardening Sprint is an anti-pattern but one that companies early in their Agile transition may have to implement. Some may always need some element of it such as a client I had with a huge amount of legacy code, very complex interactions between multiple systems, and a hardware element that would never allow for full automation. As long as you recognize why you are having to do it and have a plan to address as many of those underlying causes as you can, then I think it an acceptable (albeit hopefully temporary) practice. Those who paint it with a broad brush as a complete anti-pattern and say you should never do it usually have very flippant answers for what you should do instead. "You should automate all your tests!" Then I would like to borrow your test automation magic wand because that is not something that happens over night at most places.<br /><br />Thanks for a very in-depth article that explored both sides of this hotly debated issue.Tommy Normanhttps://www.blogger.com/profile/04525034029168813147noreply@blogger.comtag:blogger.com,1999:blog-5028009537158799436.post-5031725295014299012013-01-14T05:51:28.892-08:002013-01-14T05:51:28.892-08:00Hi Jim, my name's Rina, I'm the content ma...Hi Jim, my name's Rina, I'm the content manager at iMasters, one of the largest brazilian communities for developers. I'd like to talk to you about translating your articles to Portuguese and re-publishing them. Can you please contact me at rina.noronha@imasters.com.br? Thanks!Rina Noronhahttp://www.imasters.com.brnoreply@blogger.comtag:blogger.com,1999:blog-5028009537158799436.post-75347051869099356822013-01-11T10:47:36.101-08:002013-01-11T10:47:36.101-08:00@Anonymous, I don't necessarily see a hardenin...@Anonymous, I don't necessarily see a hardening sprint as a form of waterfall. Unless you're deploying every release to production, you need to schedule some time before deployment to take care of release-related issues. If this is the first time that you've released to production, or if it's been a long time because you're production release cycles are several months, then you'll need to spend a good amount of time getting ready - so a hardening sprint, or more than one, is going to be needed.Jim Birdhttps://www.blogger.com/profile/17371102366836131341noreply@blogger.comtag:blogger.com,1999:blog-5028009537158799436.post-75874269332759698572013-01-11T09:53:59.334-08:002013-01-11T09:53:59.334-08:00I think that this concept - hardening sprint - pro...I think that this concept - hardening sprint - probably will be used by organizations like "testing sprint", transforming it in a dysfunction of scrum (creating another mode of waterfall). Anonymousnoreply@blogger.com