Skip to main content
Project Management

Return to Answer

added 4 characters in body
Source Link
acidjunk
acidjunk
  • 111
  • 3

First off; when the team reaches the business targets; don't worry about it.

BUT

When I read the comments about working for years with Agile methodology I suspect that you are only partially implementing it. Without sprint planning, you are not using Agile.

This would be a good one to tackle on the retrospectives; as the process clearly would benefit from it. When planning is continuously on the low side: that's also something you should handle in the retrospective.

First off; when the team reaches the business targets; don't worry about it.

BUT

When I read the comments about working for years with Agile methodology I suspect that you are only partially implementing it. Without sprint planning, you are not using Agile.

This would be a good to tackle on the retrospectives; as the process clearly would benefit from it. When planning is continuously on the low side: that's also something you should handle in the retrospective.

First off; when the team reaches the business targets; don't worry about it.

BUT

When I read the comments about working for years with Agile methodology I suspect that you are only partially implementing it. Without sprint planning, you are not using Agile.

This would be a good one to tackle on the retrospectives; as the process clearly would benefit from it. When planning is continuously on the low side: that's also something you should handle in the retrospective.

edited body
Source Link
acidjunk
acidjunk
  • 111
  • 3

First off; when the team reaches the business targets; don't worry about it.

BUT

When I read the comments about working for years with Agile methodology I suspect that you are only partially implementing it. Without sprint planning, you are not using ScrumAgile.

This would be a good to tackle on the retrospectives; as the process clearly would benefit from it. When planning is continuously on the low side: that's also something you should handle in the retrospective.

First off; when the team reaches the business targets; don't worry about it.

BUT

When I read the comments about working for years with Agile methodology I suspect that you are only partially implementing it. Without sprint planning, you are not using Scrum.

This would be a good to tackle on the retrospectives; as the process clearly would benefit from it. When planning is continuously on the low side: that's also something you should handle in the retrospective.

First off; when the team reaches the business targets; don't worry about it.

BUT

When I read the comments about working for years with Agile methodology I suspect that you are only partially implementing it. Without sprint planning, you are not using Agile.

This would be a good to tackle on the retrospectives; as the process clearly would benefit from it. When planning is continuously on the low side: that's also something you should handle in the retrospective.

Source Link
acidjunk
acidjunk
  • 111
  • 3

First off; when the team reaches the business targets; don't worry about it.

BUT

When I read the comments about working for years with Agile methodology I suspect that you are only partially implementing it. Without sprint planning, you are not using Scrum.

This would be a good to tackle on the retrospectives; as the process clearly would benefit from it. When planning is continuously on the low side: that's also something you should handle in the retrospective.