Shaping Before You Build
The article discusses the concept of shaping in software development, particularly within the Shape Up methodology. It emphasizes the importance of defining the scope and boundaries of features before development begins. By doing so, teams can avoid scope creep and ensure that features are built within a reasonable timeframe.
- ▪Shaping helps bridge the gap between user stories and feasible development tasks.
- ▪Every shaped feature consists of appetite, solution, and boundaries.
- ▪A pitch is created to capture these elements and justify the feature's development.
Opening excerpt (first ~120 words) tap to expand
try { if(localStorage) { let currentUser = localStorage.getItem('current_user'); if (currentUser) { currentUser = JSON.parse(currentUser); if (currentUser.id === 95943) { document.getElementById('article-show-container').classList.add('current-user-is-article-author'); } } } } catch (e) { console.error(e); } Steve McDougall Posted on May 19 • Originally published at juststeveking.com Shaping Before You Build #shaping #scopemanagement #productthinking #planning from-requirements-to-reality (10 Part Series) 1 Stop Writing Code First 2 Reading Between the Lines ... 6 more parts...
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at DEV.to (Top).
Discussion
0 commentsMore from DEV.to (Top)
