Styjun

How do I find my Spellcasting Ability for my D&D character?

Calculation of line of sight system gain

What is "Lambda" in Heston's original paper on stochastic volatility models?

Improvising over quartal voicings

Twin's vs. Twins'

What did Turing mean when saying that "machines cannot give rise to surprises" is due to a fallacy?

Why do C and C++ allow the expression (int) + 4*5;

How can I list files in reverse time order by a command and pass them as arguments to another command?

By what mechanism was the 2017 UK General Election called?

Is there a spell that can create a permanent fire?

NIntegrate on a solution of a matrix ODE

Is this Kuo-toa homebrew race balanced?

Keep at all times, the minus sign above aligned with minus sign below

Marquee sign letters

Why does BitLocker not use RSA?

How does the body cool itself in a stillsuit?

Inverse square law not accurate for non-point masses?

Meaning of 境 in その日を境に

Determine whether an integer is a palindrome

Weaponising the Grasp-at-a-Distance spell

Is the time—manner—place ordering of adverbials an oversimplification?

Statistical analysis applied to methods coming out of Machine Learning

How do you cope with tons of web fonts when copying and pasting from web pages?

calculator's angle answer for trig ratios that can work in more than 1 quadrant on the unit circle

Guidelines for handling patch releases in TFS

.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty height:90px;width:728px;box-sizing:border-box;

-1

1

I'm working on a company which uses TFS to handle the development process. We use iterations to determine which user stories to be developed for a certain release. With other words, there is a connection between a release and an iteration in TFS. Now I'm thinking of how to handle patch releases (a release to fix bugs). Are they separate iterations or is there another way to handle them?

I have searched the Internet for guidelines how to handle patch releases without finding anything useful. Does anyone know of any guidelines to handle patch releases within TFS?

tfs patch sprint

share|improve this question

asked Mar 22 at 12:41

Janni KajbrinkJanni Kajbrink

1861312

• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  Unless you plan to issue patche releases on a regular basis (in which case, patch releases should be part of your development cadence and thus scheduled like any other iteration), they fall under the category of "hotfixes", which are by their nature out-of-band.
  
  – Daniel Mann
  Mar 22 at 14:26
  
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  But even if you make a hotfix, there should be Bugs and/or User Stories connected to the hotfix. I wonder if there are any guidelines how to handle this in TFS. Should they be attached to a separate iteration or should they be handled in a different way. I haven't found any relevant guidelines for this, which I found kind of strange as all development teams must handle this on a regular basis.
  
  – Janni Kajbrink
  Mar 22 at 18:56
  
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  Unplanned hotfixes go into the current sprint.
  
  – Daniel Mann
  Mar 22 at 18:58
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  If they go into the current sprint, how do you distinguish them from the rest of the user stories which are released in the planned release? Are there not any guidelines from the TFS team for handling these kind of situations?
  
  – Janni Kajbrink
  Mar 27 at 14:31
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  It depends on what you're trying to track and why. You can tag the work items as "hotfix", for example. Or you can add a new lane to the kanban board for "unplanned". There are a lot of options, it's all about what works best for your organization.
  
  – Daniel Mann
  Mar 27 at 16:16
  

  
  
  
  

add a comment | 

-1

1

I'm working on a company which uses TFS to handle the development process. We use iterations to determine which user stories to be developed for a certain release. With other words, there is a connection between a release and an iteration in TFS. Now I'm thinking of how to handle patch releases (a release to fix bugs). Are they separate iterations or is there another way to handle them?

I have searched the Internet for guidelines how to handle patch releases without finding anything useful. Does anyone know of any guidelines to handle patch releases within TFS?

tfs patch sprint

share|improve this question

asked Mar 22 at 12:41

Janni KajbrinkJanni Kajbrink

1861312

• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  Unless you plan to issue patche releases on a regular basis (in which case, patch releases should be part of your development cadence and thus scheduled like any other iteration), they fall under the category of "hotfixes", which are by their nature out-of-band.
  
  – Daniel Mann
  Mar 22 at 14:26
  
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  But even if you make a hotfix, there should be Bugs and/or User Stories connected to the hotfix. I wonder if there are any guidelines how to handle this in TFS. Should they be attached to a separate iteration or should they be handled in a different way. I haven't found any relevant guidelines for this, which I found kind of strange as all development teams must handle this on a regular basis.
  
  – Janni Kajbrink
  Mar 22 at 18:56
  
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  Unplanned hotfixes go into the current sprint.
  
  – Daniel Mann
  Mar 22 at 18:58
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  If they go into the current sprint, how do you distinguish them from the rest of the user stories which are released in the planned release? Are there not any guidelines from the TFS team for handling these kind of situations?
  
  – Janni Kajbrink
  Mar 27 at 14:31
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  It depends on what you're trying to track and why. You can tag the work items as "hotfix", for example. Or you can add a new lane to the kanban board for "unplanned". There are a lot of options, it's all about what works best for your organization.
  
  – Daniel Mann
  Mar 27 at 16:16
  

  
  
  
  

add a comment | 

I'm working on a company which uses TFS to handle the development process. We use iterations to determine which user stories to be developed for a certain release. With other words, there is a connection between a release and an iteration in TFS. Now I'm thinking of how to handle patch releases (a release to fix bugs). Are they separate iterations or is there another way to handle them?

I have searched the Internet for guidelines how to handle patch releases without finding anything useful. Does anyone know of any guidelines to handle patch releases within TFS?

tfs patch sprint

share|improve this question

asked Mar 22 at 12:41

Janni KajbrinkJanni Kajbrink

1861312

share|improve this question

asked Mar 22 at 12:41

Janni KajbrinkJanni Kajbrink

1861312

share|improve this question

asked Mar 22 at 12:41

Janni KajbrinkJanni Kajbrink

1861312

asked Mar 22 at 12:41

Janni KajbrinkJanni Kajbrink

1861312

asked Mar 22 at 12:41

Janni KajbrinkJanni Kajbrink

1861312