in a scrum setup we are facing several planning issues for software development:
- classifying stories by complexity numbers like fibonacci (1,3,5,8,13...) can be difficult because there are so many factors contributing
- the complexity numbers are only of limited utility for time estimation
- quarter time and capacity planning can be very inaccurate using the above
- quarter planning is affected by many other factors which are not technically related to software development
- quarter planning often has to be based on high level goals without detailed stories what are the possible measures to improve sprint and quarter (PI) planning?