Team Retrospective - [11/7/2021]

A retrospective is a way to learn from experience. It's an opportunity for a team to take a step back and reflect on how things are going, and to create a plan for itself to refine and improve for the future. This was issue was automatically created to remind the team to take time to reflect, and to provide guidance for the conversation.

Remember that retrospectives are blameless. Focus on what you can learn and improve upon for next time.

Insights

0 Merged pull requests since [11/7/2021]
1 Open pull requests since [11/7/2021]
[1] Closed issues since [11/7/2021]
[1] New issues since [11/7/2021]

Excluding merges, [1] author has pushed [1] commit to undefined and [1] commit to all branches. On [undefined], [0] files have changed and there have been [0] additions and [0] deletions.

[Profile pics of all contributors]

What went well?

It's important to notice which things went well so we can continue doing them in the future.

What could go better?

Make note of things that were okay, but not great. How could they be improved? And of course, discuss the things that just didn't go right at all. Should we stop doing this altogether? Is it expected to improve itself, and we just have to double down and get through it? Can we offset it in some other way?

What will we commit to improve in the short term?

The discussion above may reveal a bunch of things we'd like to do. But to ensure that we're not overwhelmed or changing too many things at once, let's pick a couple and then commit to them.

For best results, we'll create specific action items and assign each one to someone on the team.

Team Retrospective - [11/7/2021]

A retrospective is a way to learn from experience. It's an opportunity for a team to take a step back and reflect on how things are going, and to create a plan for itself to refine and improve for the future. This was issue was automatically created to remind the team to take time to reflect, and to provide guidance for the conversation.

Remember that retrospectives are blameless. Focus on what you can learn and improve upon for next time.

Insights

0 Merged pull requests since [11/7/2021]
1 Open pull requests since [11/7/2021]
[1] Closed issues since [11/7/2021]
[1] New issues since [11/7/2021]

Excluding merges, [1] author has pushed [1] commit to undefined and [1] commit to all branches. On [undefined], [0] files have changed and there have been [0] additions and [0] deletions.

[Profile pics of all contributors]

What went well?

It's important to notice which things went well so we can continue doing them in the future.

What could go better?

Make note of things that were okay, but not great. How could they be improved? And of course, discuss the things that just didn't go right at all. Should we stop doing this altogether? Is it expected to improve itself, and we just have to double down and get through it? Can we offset it in some other way?

What will we commit to improve in the short term?

The discussion above may reveal a bunch of things we'd like to do. But to ensure that we're not overwhelmed or changing too many things at once, let's pick a couple and then commit to them.

For best results, we'll create specific action items and assign each one to someone on the team.

Team Retrospective - [11/5/2021]

A retrospective is a way to learn from experience. It's an opportunity for a team to take a step back and reflect on how things are going, and to create a plan for itself to refine and improve for the future. This was issue was automatically created to remind the team to take time to reflect, and to provide guidance for the conversation.

Remember that retrospectives are blameless. Focus on what you can learn and improve upon for next time.

Insights

0 Merged pull requests since [11/5/2021]
1 Open pull requests since [11/5/2021]
[1] Closed issues since [11/5/2021]
[1] New issues since [11/5/2021]

Excluding merges, [1] author has pushed [1] commit to undefined and [1] commit to all branches. On [undefined], [0] files have changed and there have been [0] additions and [0] deletions.

[Profile pics of all contributors]

What went well?

It's important to notice which things went well so we can continue doing them in the future.

What could go better?

Make note of things that were okay, but not great. How could they be improved? And of course, discuss the things that just didn't go right at all. Should we stop doing this altogether? Is it expected to improve itself, and we just have to double down and get through it? Can we offset it in some other way?

What will we commit to improve in the short term?

The discussion above may reveal a bunch of things we'd like to do. But to ensure that we're not overwhelmed or changing too many things at once, let's pick a couple and then commit to them.

For best results, we'll create specific action items and assign each one to someone on the team.

Team Retrospective - [11/7/2021]

A retrospective is a way to learn from experience. It's an opportunity for a team to take a step back and reflect on how things are going, and to create a plan for itself to refine and improve for the future. This was issue was automatically created to remind the team to take time to reflect, and to provide guidance for the conversation.

Remember that retrospectives are blameless. Focus on what you can learn and improve upon for next time.

Insights

0 Merged pull requests since [11/7/2021]
1 Open pull requests since [11/7/2021]
[1] Closed issues since [11/7/2021]
[1] New issues since [11/7/2021]

Excluding merges, [1] author has pushed [1] commit to undefined and [1] commit to all branches. On [undefined], [0] files have changed and there have been [0] additions and [0] deletions.

[Profile pics of all contributors]

What went well?

It's important to notice which things went well so we can continue doing them in the future.

What could go better?

Make note of things that were okay, but not great. How could they be improved? And of course, discuss the things that just didn't go right at all. Should we stop doing this altogether? Is it expected to improve itself, and we just have to double down and get through it? Can we offset it in some other way?

What will we commit to improve in the short term?

The discussion above may reveal a bunch of things we'd like to do. But to ensure that we're not overwhelmed or changing too many things at once, let's pick a couple and then commit to them.

For best results, we'll create specific action items and assign each one to someone on the team.

Team Retrospective - [11/7/2021]

A retrospective is a way to learn from experience. It's an opportunity for a team to take a step back and reflect on how things are going, and to create a plan for itself to refine and improve for the future. This was issue was automatically created to remind the team to take time to reflect, and to provide guidance for the conversation.

Remember that retrospectives are blameless. Focus on what you can learn and improve upon for next time.

Insights

0 Merged pull requests since [11/7/2021]
1 Open pull requests since [11/7/2021]
[1] Closed issues since [11/7/2021]
[1] New issues since [11/7/2021]

Excluding merges, [1] author has pushed [1] commit to undefined and [1] commit to all branches. On [undefined], [0] files have changed and there have been [0] additions and [0] deletions.

[Profile pics of all contributors]

What went well?

It's important to notice which things went well so we can continue doing them in the future.

What could go better?

Make note of things that were okay, but not great. How could they be improved? And of course, discuss the things that just didn't go right at all. Should we stop doing this altogether? Is it expected to improve itself, and we just have to double down and get through it? Can we offset it in some other way?

What will we commit to improve in the short term?

The discussion above may reveal a bunch of things we'd like to do. But to ensure that we're not overwhelmed or changing too many things at once, let's pick a couple and then commit to them.

For best results, we'll create specific action items and assign each one to someone on the team.

Team Retrospective - [11/7/2021]

A retrospective is a way to learn from experience. It's an opportunity for a team to take a step back and reflect on how things are going, and to create a plan for itself to refine and improve for the future. This was issue was automatically created to remind the team to take time to reflect, and to provide guidance for the conversation.

Remember that retrospectives are blameless. Focus on what you can learn and improve upon for next time.

Insights

0 Merged pull requests since [11/7/2021]
1 Open pull requests since [11/7/2021]
0 Closed issues since [11/7/2021]
9 New issues since [11/7/2021]

Excluding merges, [1] author has pushed [1] commit to undefined and [1] commit to all branches. On [undefined], [0] files have changed and there have been [0] additions and [0] deletions.

[Profile pics of all contributors]

What went well?

It's important to notice which things went well so we can continue doing them in the future.

What could go better?

Make note of things that were okay, but not great. How could they be improved? And of course, discuss the things that just didn't go right at all. Should we stop doing this altogether? Is it expected to improve itself, and we just have to double down and get through it? Can we offset it in some other way?

What will we commit to improve in the short term?

The discussion above may reveal a bunch of things we'd like to do. But to ensure that we're not overwhelmed or changing too many things at once, let's pick a couple and then commit to them.

For best results, we'll create specific action items and assign each one to someone on the team.

Team Retrospective - [11/7/2021]

A retrospective is a way to learn from experience. It's an opportunity for a team to take a step back and reflect on how things are going, and to create a plan for itself to refine and improve for the future. This was issue was automatically created to remind the team to take time to reflect, and to provide guidance for the conversation.

Remember that retrospectives are blameless. Focus on what you can learn and improve upon for next time.

Insights

0 Merged pull requests since [11/7/2021]
1 Open pull requests since [11/7/2021]
0 Closed issues since [11/7/2021]
8 New issues since [11/7/2021]

Excluding merges, [1] author has pushed [1] commit to undefined and [1] commit to all branches. On [undefined], [0] files have changed and there have been [0] additions and [0] deletions.

[Profile pics of all contributors]

What went well?

It's important to notice which things went well so we can continue doing them in the future.

What could go better?

Make note of things that were okay, but not great. How could they be improved? And of course, discuss the things that just didn't go right at all. Should we stop doing this altogether? Is it expected to improve itself, and we just have to double down and get through it? Can we offset it in some other way?

What will we commit to improve in the short term?

The discussion above may reveal a bunch of things we'd like to do. But to ensure that we're not overwhelmed or changing too many things at once, let's pick a couple and then commit to them.

For best results, we'll create specific action items and assign each one to someone on the team.

Team Retrospective - [11/7/2021]

A retrospective is a way to learn from experience. It's an opportunity for a team to take a step back and reflect on how things are going, and to create a plan for itself to refine and improve for the future. This was issue was automatically created to remind the team to take time to reflect, and to provide guidance for the conversation.

Remember that retrospectives are blameless. Focus on what you can learn and improve upon for next time.

Insights

0 Merged pull requests since [11/7/2021]
1 Open pull requests since [11/7/2021]
[1] Closed issues since [11/7/2021]
[1] New issues since [11/7/2021]

Excluding merges, [1] author has pushed [1] commit to undefined and [1] commit to all branches. On [undefined], [0] files have changed and there have been [0] additions and [0] deletions.

[Profile pics of all contributors]

What went well?

It's important to notice which things went well so we can continue doing them in the future.

What could go better?

Make note of things that were okay, but not great. How could they be improved? And of course, discuss the things that just didn't go right at all. Should we stop doing this altogether? Is it expected to improve itself, and we just have to double down and get through it? Can we offset it in some other way?

What will we commit to improve in the short term?

The discussion above may reveal a bunch of things we'd like to do. But to ensure that we're not overwhelmed or changing too many things at once, let's pick a couple and then commit to them.

For best results, we'll create specific action items and assign each one to someone on the team.

Team Retrospective - [11/7/2021]

A retrospective is a way to learn from experience. It's an opportunity for a team to take a step back and reflect on how things are going, and to create a plan for itself to refine and improve for the future. This was issue was automatically created to remind the team to take time to reflect, and to provide guidance for the conversation.

Remember that retrospectives are blameless. Focus on what you can learn and improve upon for next time.

Insights

0 Merged pull requests since [11/7/2021]
1 Open pull requests since [11/7/2021]
[1] Closed issues since [11/7/2021]
[1] New issues since [11/7/2021]

Excluding merges, [1] author has pushed [1] commit to undefined and [1] commit to all branches. On [undefined], [0] files have changed and there have been [0] additions and [0] deletions.

[Profile pics of all contributors]

What went well?

It's important to notice which things went well so we can continue doing them in the future.

What could go better?

Make note of things that were okay, but not great. How could they be improved? And of course, discuss the things that just didn't go right at all. Should we stop doing this altogether? Is it expected to improve itself, and we just have to double down and get through it? Can we offset it in some other way?

What will we commit to improve in the short term?

The discussion above may reveal a bunch of things we'd like to do. But to ensure that we're not overwhelmed or changing too many things at once, let's pick a couple and then commit to them.

For best results, we'll create specific action items and assign each one to someone on the team.

Team Retrospective - [11/7/2021]

A retrospective is a way to learn from experience. It's an opportunity for a team to take a step back and reflect on how things are going, and to create a plan for itself to refine and improve for the future. This was issue was automatically created to remind the team to take time to reflect, and to provide guidance for the conversation.

Remember that retrospectives are blameless. Focus on what you can learn and improve upon for next time.

Insights

0 Merged pull requests since [11/7/2021]
1 Open pull requests since [11/7/2021]
0 Closed issues since [11/7/2021]
7 New issues since [11/7/2021]

Excluding merges, [1] author has pushed [1] commit to undefined and [1] commit to all branches. On [undefined], [0] files have changed and there have been [0] additions and [0] deletions.

[Profile pics of all contributors]

What went well?

It's important to notice which things went well so we can continue doing them in the future.

What could go better?

Make note of things that were okay, but not great. How could they be improved? And of course, discuss the things that just didn't go right at all. Should we stop doing this altogether? Is it expected to improve itself, and we just have to double down and get through it? Can we offset it in some other way?

What will we commit to improve in the short term?

The discussion above may reveal a bunch of things we'd like to do. But to ensure that we're not overwhelmed or changing too many things at once, let's pick a couple and then commit to them.

For best results, we'll create specific action items and assign each one to someone on the team.

juniorjp / spike-retro-actions Goto Github PK

spike-retro-actions's People

Contributors

Watchers

spike-retro-actions's Issues

Team Retrospective - [11/7/2021]

Insights

What went well?

What could go better?

What will we commit to improve in the short term?

Team Retrospective - [11/7/2021]

Insights

What went well?

What could go better?

What will we commit to improve in the short term?

Team Retrospective - [11/5/2021]

Insights

What went well?

What could go better?

What will we commit to improve in the short term?

Team Retrospective - [11/7/2021]

Insights

What went well?

What could go better?

What will we commit to improve in the short term?

Team Retrospective - [11/7/2021]

Insights

What went well?

What could go better?

What will we commit to improve in the short term?

Team Retrospective - [11/7/2021]

Insights

What went well?

What could go better?

What will we commit to improve in the short term?

Team Retrospective - [11/7/2021]

Insights

What went well?

What could go better?

What will we commit to improve in the short term?

Team Retrospective - [11/7/2021]

Insights

What went well?

What could go better?

What will we commit to improve in the short term?

Team Retrospective - [11/7/2021]

Insights

What went well?

What could go better?

What will we commit to improve in the short term?

Team Retrospective - [11/7/2021]

Insights

What went well?

What could go better?

What will we commit to improve in the short term?

Recommend Projects

Recommend Topics

Recommend Org