Monthly twice production release for my software project The Next CEO of Stack OverflowWhat techniques are effective for Scrum teams within organizations that do waterfall release planning?How frequently can a release happen within a Scrum Sprint?Why does our Sprint Planning not align with our original Release Plan?Do people use sticky notes for release planning still?How to make Release Planning more accurate?Team velocity dramatically slows down to the end of a sprintWho performs a release and how is it estimated?Scrum certification for Release manager managing agile releasesIs it correct to create pre-release versions in Jira?How can I know if my app is ready for beta release?

Help/tips for a first time writer?

How to set page number in right side in chapter title page?

Help understanding this unsettling image of Titan, Epimetheus, and Saturn's rings?

Getting Stale Gas Out of a Gas Tank w/out Dropping the Tank

Audio Conversion With ADS1243

Prepend last line of stdin to entire stdin

Is there a way to save my career from absolute disaster?

Spaces in which all closed sets are regular closed

Can someone explain this formula for calculating Manhattan distance?

IC has pull-down resistors on SMBus lines?

Do scriptures give a method to recognize a truly self-realized person/jivanmukta?

Would a completely good Muggle be able to use a wand?

What can the phrase “is embedded in a whale of a bill” mean?

Film where the government was corrupt with aliens, people sent to kill aliens are given rigged visors not showing the right aliens

Is it ever safe to open a suspicious HTML file (e.g. email attachment)?

Why don't programming languages automatically manage the synchronous/asynchronous problem?

How to avoid supervisors with prejudiced views?

Can Sneak Attack be used when hitting with an improvised weapon?

Why is the US ranked as #45 in Press Freedom ratings, despite its extremely permissive free speech laws?

Strange use of "whether ... than ..." in official text

Does the Idaho Potato Commission associate potato skins with healthy eating?

Physiological effects of huge anime eyes

Is there a reasonable and studied concept of reduction between regular languages?

Purpose of level-shifter with same in and out voltages



Monthly twice production release for my software project



The Next CEO of Stack OverflowWhat techniques are effective for Scrum teams within organizations that do waterfall release planning?How frequently can a release happen within a Scrum Sprint?Why does our Sprint Planning not align with our original Release Plan?Do people use sticky notes for release planning still?How to make Release Planning more accurate?Team velocity dramatically slows down to the end of a sprintWho performs a release and how is it estimated?Scrum certification for Release manager managing agile releasesIs it correct to create pre-release versions in Jira?How can I know if my app is ready for beta release?










6















I am working as a product owner in a fintech based software company. My development team follows scrum methodology and 2 weeks sprint. They tried to follow scrum ceremony but not to do story estimation. From my stakeholder they set 1 monthly production release each month, say 25th of each month and some time any hotfix release. Our release cycle is much complex. First QA test the feature in SIT in environment. After get the signed off fron SIT qa, dev team build the package and send it to devips for UAT deployment. After UAT deployment, UAT tester test the build items (one thing to mention, UAT deployment only happen at time of product release not after each sprint deliverable.). If UAT tester found issue then it get backs to dev team, but they are in middle of sprint and doing some other work. Then dev team fixes the issues raise by UAT tester and send it to them again. Finally signed off from UAT it goes for production.
This is the whole scenario for our production pipeline.



Now my question how could I streamline the process. As development team got frustrated that they need to work sometimes in the middle of the sprint for bug fix or priority. Need guideline/expert opinion to manage production release properly with follow sprint.










share|improve this question







New contributor




Toufiq Mahmud is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.















  • 2





    Since, we are talking Fintech: what is actually the risk if the software has a serious bug? Millions? Billions? Then you should consider if a methodology for safety critical software might be preferable over an agile process.

    – lalala
    2 days ago











  • Yes thats true, but Agile is most popular and my management knows it well. And I believe my problem is common and many experience this.

    – Toufiq Mahmud
    yesterday











  • How many people is there on the whole development + QA + infrastructure team?

    – Tiago Cardoso
    yesterday











  • @lalala: We are actually using an agile process to build safety critical software (of the sort that needs to be officially certified), so the two don't exclude each other.

    – Bart van Ingen Schenau
    yesterday















6















I am working as a product owner in a fintech based software company. My development team follows scrum methodology and 2 weeks sprint. They tried to follow scrum ceremony but not to do story estimation. From my stakeholder they set 1 monthly production release each month, say 25th of each month and some time any hotfix release. Our release cycle is much complex. First QA test the feature in SIT in environment. After get the signed off fron SIT qa, dev team build the package and send it to devips for UAT deployment. After UAT deployment, UAT tester test the build items (one thing to mention, UAT deployment only happen at time of product release not after each sprint deliverable.). If UAT tester found issue then it get backs to dev team, but they are in middle of sprint and doing some other work. Then dev team fixes the issues raise by UAT tester and send it to them again. Finally signed off from UAT it goes for production.
This is the whole scenario for our production pipeline.



Now my question how could I streamline the process. As development team got frustrated that they need to work sometimes in the middle of the sprint for bug fix or priority. Need guideline/expert opinion to manage production release properly with follow sprint.










share|improve this question







New contributor




Toufiq Mahmud is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.















  • 2





    Since, we are talking Fintech: what is actually the risk if the software has a serious bug? Millions? Billions? Then you should consider if a methodology for safety critical software might be preferable over an agile process.

    – lalala
    2 days ago











  • Yes thats true, but Agile is most popular and my management knows it well. And I believe my problem is common and many experience this.

    – Toufiq Mahmud
    yesterday











  • How many people is there on the whole development + QA + infrastructure team?

    – Tiago Cardoso
    yesterday











  • @lalala: We are actually using an agile process to build safety critical software (of the sort that needs to be officially certified), so the two don't exclude each other.

    – Bart van Ingen Schenau
    yesterday













6












6








6








I am working as a product owner in a fintech based software company. My development team follows scrum methodology and 2 weeks sprint. They tried to follow scrum ceremony but not to do story estimation. From my stakeholder they set 1 monthly production release each month, say 25th of each month and some time any hotfix release. Our release cycle is much complex. First QA test the feature in SIT in environment. After get the signed off fron SIT qa, dev team build the package and send it to devips for UAT deployment. After UAT deployment, UAT tester test the build items (one thing to mention, UAT deployment only happen at time of product release not after each sprint deliverable.). If UAT tester found issue then it get backs to dev team, but they are in middle of sprint and doing some other work. Then dev team fixes the issues raise by UAT tester and send it to them again. Finally signed off from UAT it goes for production.
This is the whole scenario for our production pipeline.



Now my question how could I streamline the process. As development team got frustrated that they need to work sometimes in the middle of the sprint for bug fix or priority. Need guideline/expert opinion to manage production release properly with follow sprint.










share|improve this question







New contributor




Toufiq Mahmud is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.












I am working as a product owner in a fintech based software company. My development team follows scrum methodology and 2 weeks sprint. They tried to follow scrum ceremony but not to do story estimation. From my stakeholder they set 1 monthly production release each month, say 25th of each month and some time any hotfix release. Our release cycle is much complex. First QA test the feature in SIT in environment. After get the signed off fron SIT qa, dev team build the package and send it to devips for UAT deployment. After UAT deployment, UAT tester test the build items (one thing to mention, UAT deployment only happen at time of product release not after each sprint deliverable.). If UAT tester found issue then it get backs to dev team, but they are in middle of sprint and doing some other work. Then dev team fixes the issues raise by UAT tester and send it to them again. Finally signed off from UAT it goes for production.
This is the whole scenario for our production pipeline.



Now my question how could I streamline the process. As development team got frustrated that they need to work sometimes in the middle of the sprint for bug fix or priority. Need guideline/expert opinion to manage production release properly with follow sprint.







release-plan






share|improve this question







New contributor




Toufiq Mahmud is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.











share|improve this question







New contributor




Toufiq Mahmud is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.









share|improve this question




share|improve this question






New contributor




Toufiq Mahmud is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.









asked 2 days ago









Toufiq MahmudToufiq Mahmud

313




313




New contributor




Toufiq Mahmud is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.





New contributor





Toufiq Mahmud is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.






Toufiq Mahmud is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.







  • 2





    Since, we are talking Fintech: what is actually the risk if the software has a serious bug? Millions? Billions? Then you should consider if a methodology for safety critical software might be preferable over an agile process.

    – lalala
    2 days ago











  • Yes thats true, but Agile is most popular and my management knows it well. And I believe my problem is common and many experience this.

    – Toufiq Mahmud
    yesterday











  • How many people is there on the whole development + QA + infrastructure team?

    – Tiago Cardoso
    yesterday











  • @lalala: We are actually using an agile process to build safety critical software (of the sort that needs to be officially certified), so the two don't exclude each other.

    – Bart van Ingen Schenau
    yesterday












  • 2





    Since, we are talking Fintech: what is actually the risk if the software has a serious bug? Millions? Billions? Then you should consider if a methodology for safety critical software might be preferable over an agile process.

    – lalala
    2 days ago











  • Yes thats true, but Agile is most popular and my management knows it well. And I believe my problem is common and many experience this.

    – Toufiq Mahmud
    yesterday











  • How many people is there on the whole development + QA + infrastructure team?

    – Tiago Cardoso
    yesterday











  • @lalala: We are actually using an agile process to build safety critical software (of the sort that needs to be officially certified), so the two don't exclude each other.

    – Bart van Ingen Schenau
    yesterday







2




2





Since, we are talking Fintech: what is actually the risk if the software has a serious bug? Millions? Billions? Then you should consider if a methodology for safety critical software might be preferable over an agile process.

– lalala
2 days ago





Since, we are talking Fintech: what is actually the risk if the software has a serious bug? Millions? Billions? Then you should consider if a methodology for safety critical software might be preferable over an agile process.

– lalala
2 days ago













Yes thats true, but Agile is most popular and my management knows it well. And I believe my problem is common and many experience this.

– Toufiq Mahmud
yesterday





Yes thats true, but Agile is most popular and my management knows it well. And I believe my problem is common and many experience this.

– Toufiq Mahmud
yesterday













How many people is there on the whole development + QA + infrastructure team?

– Tiago Cardoso
yesterday





How many people is there on the whole development + QA + infrastructure team?

– Tiago Cardoso
yesterday













@lalala: We are actually using an agile process to build safety critical software (of the sort that needs to be officially certified), so the two don't exclude each other.

– Bart van Ingen Schenau
yesterday





@lalala: We are actually using an agile process to build safety critical software (of the sort that needs to be officially certified), so the two don't exclude each other.

– Bart van Ingen Schenau
yesterday










2 Answers
2






active

oldest

votes


















4














I second ctrl-atl-delor (+1!) - you should invest on automation.



Agile methodology helps on how work is organized, but regardless of the methodology, you should automate as much as possible of your work.



We have a similar scenario in our project - and I'd guess it's fairly common on legacy applications.



You have two main fronts of work:



  • SDLC automation: Continuous Integration, Delivery and Deployment

  • Testing automation: BDD and TDD might be helpful.

Based on your scenario, you'll need to assess which areas within SDLC or Testing automation you can obtain benefits faster (the low-hanging fruits).



You'll need support from either C-level and / or stakeholders, as you'll definitely need to invest time and effort on it.






share|improve this answer























  • Yes, I agree with you. Automation and Test driven development could solve most of my pains. But its way to go. Need alignment with my management

    – Toufiq Mahmud
    yesterday











  • If your scenario is similar to mine, one of the key points is to define the items to deliver to UAT, how to identify them and ensure they're tested. That can be achieved with more (lightweight) process.

    – Tiago Cardoso
    yesterday


















3














Well done you are doing a grate job. Scrum has lead you to diagnose several problems with your process.



I would recommend devops, developers and ops merge. They then fully deploy to testing (that is the same as operational). After testing you press a button to deploy to operational. Docker is a good tool to help with this.



The other thing (and most important thing) is to conduct a retrospective, when ever you detect a problem (feed back from test: Why did this happen? incomplete/secret spec?, incomplete developer testing?)



In a retrospective ask questions, without blame. When asking use 5-why. That is ask why, then ask why (5 times). E.g. Why did it break? It broke because we over loaded the donkey. Why did we over load the donkey? Because we did not know how much load we were putting on it. Why? because the scales where missing. Why? because they were being borrowed by bill. Why? Because bill does not have his own scales. Why? because of budget savings. Why? because …






share|improve this answer

























  • I think you missed the most important question from the feedback - how do we make sure this never happens again? Knowing how it happened doesn't help if you don't take action to stop it happening again.

    – UKMonkey
    2 days ago











  • @UKMonkey I added a bit on retrospectives.

    – ctrl-alt-delor
    2 days ago











  • @ctrl-alt-delor Thank you

    – Toufiq Mahmud
    yesterday











Your Answer








StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "208"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);

else
createEditor();

);

function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
noCode: true, onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);



);






Toufiq Mahmud is a new contributor. Be nice, and check out our Code of Conduct.









draft saved

draft discarded


















StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fpm.stackexchange.com%2fquestions%2f26094%2fmonthly-twice-production-release-for-my-software-project%23new-answer', 'question_page');

);

Post as a guest















Required, but never shown

























2 Answers
2






active

oldest

votes








2 Answers
2






active

oldest

votes









active

oldest

votes






active

oldest

votes









4














I second ctrl-atl-delor (+1!) - you should invest on automation.



Agile methodology helps on how work is organized, but regardless of the methodology, you should automate as much as possible of your work.



We have a similar scenario in our project - and I'd guess it's fairly common on legacy applications.



You have two main fronts of work:



  • SDLC automation: Continuous Integration, Delivery and Deployment

  • Testing automation: BDD and TDD might be helpful.

Based on your scenario, you'll need to assess which areas within SDLC or Testing automation you can obtain benefits faster (the low-hanging fruits).



You'll need support from either C-level and / or stakeholders, as you'll definitely need to invest time and effort on it.






share|improve this answer























  • Yes, I agree with you. Automation and Test driven development could solve most of my pains. But its way to go. Need alignment with my management

    – Toufiq Mahmud
    yesterday











  • If your scenario is similar to mine, one of the key points is to define the items to deliver to UAT, how to identify them and ensure they're tested. That can be achieved with more (lightweight) process.

    – Tiago Cardoso
    yesterday















4














I second ctrl-atl-delor (+1!) - you should invest on automation.



Agile methodology helps on how work is organized, but regardless of the methodology, you should automate as much as possible of your work.



We have a similar scenario in our project - and I'd guess it's fairly common on legacy applications.



You have two main fronts of work:



  • SDLC automation: Continuous Integration, Delivery and Deployment

  • Testing automation: BDD and TDD might be helpful.

Based on your scenario, you'll need to assess which areas within SDLC or Testing automation you can obtain benefits faster (the low-hanging fruits).



You'll need support from either C-level and / or stakeholders, as you'll definitely need to invest time and effort on it.






share|improve this answer























  • Yes, I agree with you. Automation and Test driven development could solve most of my pains. But its way to go. Need alignment with my management

    – Toufiq Mahmud
    yesterday











  • If your scenario is similar to mine, one of the key points is to define the items to deliver to UAT, how to identify them and ensure they're tested. That can be achieved with more (lightweight) process.

    – Tiago Cardoso
    yesterday













4












4








4







I second ctrl-atl-delor (+1!) - you should invest on automation.



Agile methodology helps on how work is organized, but regardless of the methodology, you should automate as much as possible of your work.



We have a similar scenario in our project - and I'd guess it's fairly common on legacy applications.



You have two main fronts of work:



  • SDLC automation: Continuous Integration, Delivery and Deployment

  • Testing automation: BDD and TDD might be helpful.

Based on your scenario, you'll need to assess which areas within SDLC or Testing automation you can obtain benefits faster (the low-hanging fruits).



You'll need support from either C-level and / or stakeholders, as you'll definitely need to invest time and effort on it.






share|improve this answer













I second ctrl-atl-delor (+1!) - you should invest on automation.



Agile methodology helps on how work is organized, but regardless of the methodology, you should automate as much as possible of your work.



We have a similar scenario in our project - and I'd guess it's fairly common on legacy applications.



You have two main fronts of work:



  • SDLC automation: Continuous Integration, Delivery and Deployment

  • Testing automation: BDD and TDD might be helpful.

Based on your scenario, you'll need to assess which areas within SDLC or Testing automation you can obtain benefits faster (the low-hanging fruits).



You'll need support from either C-level and / or stakeholders, as you'll definitely need to invest time and effort on it.







share|improve this answer












share|improve this answer



share|improve this answer










answered 2 days ago









Tiago CardosoTiago Cardoso

5,45231852




5,45231852












  • Yes, I agree with you. Automation and Test driven development could solve most of my pains. But its way to go. Need alignment with my management

    – Toufiq Mahmud
    yesterday











  • If your scenario is similar to mine, one of the key points is to define the items to deliver to UAT, how to identify them and ensure they're tested. That can be achieved with more (lightweight) process.

    – Tiago Cardoso
    yesterday

















  • Yes, I agree with you. Automation and Test driven development could solve most of my pains. But its way to go. Need alignment with my management

    – Toufiq Mahmud
    yesterday











  • If your scenario is similar to mine, one of the key points is to define the items to deliver to UAT, how to identify them and ensure they're tested. That can be achieved with more (lightweight) process.

    – Tiago Cardoso
    yesterday
















Yes, I agree with you. Automation and Test driven development could solve most of my pains. But its way to go. Need alignment with my management

– Toufiq Mahmud
yesterday





Yes, I agree with you. Automation and Test driven development could solve most of my pains. But its way to go. Need alignment with my management

– Toufiq Mahmud
yesterday













If your scenario is similar to mine, one of the key points is to define the items to deliver to UAT, how to identify them and ensure they're tested. That can be achieved with more (lightweight) process.

– Tiago Cardoso
yesterday





If your scenario is similar to mine, one of the key points is to define the items to deliver to UAT, how to identify them and ensure they're tested. That can be achieved with more (lightweight) process.

– Tiago Cardoso
yesterday











3














Well done you are doing a grate job. Scrum has lead you to diagnose several problems with your process.



I would recommend devops, developers and ops merge. They then fully deploy to testing (that is the same as operational). After testing you press a button to deploy to operational. Docker is a good tool to help with this.



The other thing (and most important thing) is to conduct a retrospective, when ever you detect a problem (feed back from test: Why did this happen? incomplete/secret spec?, incomplete developer testing?)



In a retrospective ask questions, without blame. When asking use 5-why. That is ask why, then ask why (5 times). E.g. Why did it break? It broke because we over loaded the donkey. Why did we over load the donkey? Because we did not know how much load we were putting on it. Why? because the scales where missing. Why? because they were being borrowed by bill. Why? Because bill does not have his own scales. Why? because of budget savings. Why? because …






share|improve this answer

























  • I think you missed the most important question from the feedback - how do we make sure this never happens again? Knowing how it happened doesn't help if you don't take action to stop it happening again.

    – UKMonkey
    2 days ago











  • @UKMonkey I added a bit on retrospectives.

    – ctrl-alt-delor
    2 days ago











  • @ctrl-alt-delor Thank you

    – Toufiq Mahmud
    yesterday















3














Well done you are doing a grate job. Scrum has lead you to diagnose several problems with your process.



I would recommend devops, developers and ops merge. They then fully deploy to testing (that is the same as operational). After testing you press a button to deploy to operational. Docker is a good tool to help with this.



The other thing (and most important thing) is to conduct a retrospective, when ever you detect a problem (feed back from test: Why did this happen? incomplete/secret spec?, incomplete developer testing?)



In a retrospective ask questions, without blame. When asking use 5-why. That is ask why, then ask why (5 times). E.g. Why did it break? It broke because we over loaded the donkey. Why did we over load the donkey? Because we did not know how much load we were putting on it. Why? because the scales where missing. Why? because they were being borrowed by bill. Why? Because bill does not have his own scales. Why? because of budget savings. Why? because …






share|improve this answer

























  • I think you missed the most important question from the feedback - how do we make sure this never happens again? Knowing how it happened doesn't help if you don't take action to stop it happening again.

    – UKMonkey
    2 days ago











  • @UKMonkey I added a bit on retrospectives.

    – ctrl-alt-delor
    2 days ago











  • @ctrl-alt-delor Thank you

    – Toufiq Mahmud
    yesterday













3












3








3







Well done you are doing a grate job. Scrum has lead you to diagnose several problems with your process.



I would recommend devops, developers and ops merge. They then fully deploy to testing (that is the same as operational). After testing you press a button to deploy to operational. Docker is a good tool to help with this.



The other thing (and most important thing) is to conduct a retrospective, when ever you detect a problem (feed back from test: Why did this happen? incomplete/secret spec?, incomplete developer testing?)



In a retrospective ask questions, without blame. When asking use 5-why. That is ask why, then ask why (5 times). E.g. Why did it break? It broke because we over loaded the donkey. Why did we over load the donkey? Because we did not know how much load we were putting on it. Why? because the scales where missing. Why? because they were being borrowed by bill. Why? Because bill does not have his own scales. Why? because of budget savings. Why? because …






share|improve this answer















Well done you are doing a grate job. Scrum has lead you to diagnose several problems with your process.



I would recommend devops, developers and ops merge. They then fully deploy to testing (that is the same as operational). After testing you press a button to deploy to operational. Docker is a good tool to help with this.



The other thing (and most important thing) is to conduct a retrospective, when ever you detect a problem (feed back from test: Why did this happen? incomplete/secret spec?, incomplete developer testing?)



In a retrospective ask questions, without blame. When asking use 5-why. That is ask why, then ask why (5 times). E.g. Why did it break? It broke because we over loaded the donkey. Why did we over load the donkey? Because we did not know how much load we were putting on it. Why? because the scales where missing. Why? because they were being borrowed by bill. Why? Because bill does not have his own scales. Why? because of budget savings. Why? because …







share|improve this answer














share|improve this answer



share|improve this answer








edited 2 days ago

























answered 2 days ago









ctrl-alt-delorctrl-alt-delor

243110




243110












  • I think you missed the most important question from the feedback - how do we make sure this never happens again? Knowing how it happened doesn't help if you don't take action to stop it happening again.

    – UKMonkey
    2 days ago











  • @UKMonkey I added a bit on retrospectives.

    – ctrl-alt-delor
    2 days ago











  • @ctrl-alt-delor Thank you

    – Toufiq Mahmud
    yesterday

















  • I think you missed the most important question from the feedback - how do we make sure this never happens again? Knowing how it happened doesn't help if you don't take action to stop it happening again.

    – UKMonkey
    2 days ago











  • @UKMonkey I added a bit on retrospectives.

    – ctrl-alt-delor
    2 days ago











  • @ctrl-alt-delor Thank you

    – Toufiq Mahmud
    yesterday
















I think you missed the most important question from the feedback - how do we make sure this never happens again? Knowing how it happened doesn't help if you don't take action to stop it happening again.

– UKMonkey
2 days ago





I think you missed the most important question from the feedback - how do we make sure this never happens again? Knowing how it happened doesn't help if you don't take action to stop it happening again.

– UKMonkey
2 days ago













@UKMonkey I added a bit on retrospectives.

– ctrl-alt-delor
2 days ago





@UKMonkey I added a bit on retrospectives.

– ctrl-alt-delor
2 days ago













@ctrl-alt-delor Thank you

– Toufiq Mahmud
yesterday





@ctrl-alt-delor Thank you

– Toufiq Mahmud
yesterday










Toufiq Mahmud is a new contributor. Be nice, and check out our Code of Conduct.









draft saved

draft discarded


















Toufiq Mahmud is a new contributor. Be nice, and check out our Code of Conduct.












Toufiq Mahmud is a new contributor. Be nice, and check out our Code of Conduct.











Toufiq Mahmud is a new contributor. Be nice, and check out our Code of Conduct.














Thanks for contributing an answer to Project Management Stack Exchange!


  • Please be sure to answer the question. Provide details and share your research!

But avoid


  • Asking for help, clarification, or responding to other answers.

  • Making statements based on opinion; back them up with references or personal experience.

To learn more, see our tips on writing great answers.




draft saved


draft discarded














StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fpm.stackexchange.com%2fquestions%2f26094%2fmonthly-twice-production-release-for-my-software-project%23new-answer', 'question_page');

);

Post as a guest















Required, but never shown





















































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown

































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown







Popular posts from this blog

Sum ergo cogito? 1 nng

三茅街道4182Guuntc Dn precexpngmageondP