--- robots: noindex, nofollow tags: pitch --- For instructions on shaping a project see here: [Shaping a Project](/kX02SXVbS6KzMOQd56i6Cg) # Improving the Shield Process ### Problem *From: [Problem guidance](https://basecamp.com/shapeup/1.5-chapter-06#ingredient-1-problem)* Shield is currently time consuming and may differ significantly depending on who is on it. It's a big resource sync and there may be ways to improve it if we had a better process. Currently there are lots of possibile fixes, but making that into a concrete task has proved difficult. Several key improvements to our process are would be: 1. What process should we have to handle the backlog? 2. What process should we use to triage new issues? 3. What process should we have to handle new features? ### Appetite *From: [Appetite guidance](https://basecamp.com/shapeup/1.5-chapter-06#ingredient-2-appetite)* 2 Weeks. This is investigatory in nature and there will always be more data to gather so a shorter time could be benefitial. Additionally, it is unlikely that there will be one "correct" answer. We will ultimately need to make an arbitrary choice as long as we are aware of potential pitfalls and limitations. ### Solution Information should be gathered from 4 places. 1. External repos that have a detailed triage process. 2. Internally, devs that have been on shield should be interviewed 3. Data from the repo, what kinds of issues do we have, what kinds have stayed open. 4. What kinds of internal processes do we already have. * Why aren't they being used? * [Current Internal Process](https://microsoft.sharepoint.com/teams/FabricTactical/_layouts/OneNote.aspx?id=%2Fteams%2FFabricTactical%2FSiteAssets%2FFabricTactical%20Notebook&wd=target%28Fabric%20Shield.one%7C32C55A18-FD42-47F3-B27D-077BFA210EE9%2F%29) Key Questions: * How do we say no to bugs and features? * Clear guidelines are probably important External repos might have questions like the following: * How do they categorize issues * How detailed is there triage process * Who does the triage process * Who puts in the fixes * What does their process outline look like * Do they use tags extensively. * How do they decide when an issue should be closed Internally we might ask the following of developers: * What takes up the most time while a person is on shield * What components take up the most time ### Risks (Rabbit holes) *From: [Rabbit hole guidance](https://basecamp.com/shapeup/1.5-chapter-06#ingredient-4-rabbit-holes)* ### Out of scope (No-gos) *From: [No-gos guidance](https://basecamp.com/shapeup/1.5-chapter-06#ingredient-5-no-gos)* Anything not related to fact finding and synthesis. Writing a process. Implementing changes .