S2ESC Strategies & Tactics

1. S2ESC Strategies & Tactics John Walz, Chuck Walrad F2F @ San Diego, CA 10-Feb-2010 Feb-2010 Walz 1

2. Strategy Development Using Knowledge-Based Dialogue and Decision-Making Relevant Environment Operational Planning Strategic Planning *Envisioned Future *Core Ideology 30 Years - 20 Years - 10 Years - 5 Years - 3 Years - 1 Year ANNUAL CONTINUOUS Goals Objectives Strategies Strategic Principles Organizational Strategy Annual Strategic Plan Review Priority Setting Program Planning Annual Operational and Budgeting Cycle Core Purpose Core Values Envisioned Future Goal Vivid Description Assumptions About The Future Mega Issues Value Discipline REVIEW ADJUSTMENT A Process for Planning and Thinking Strategically 12-Nov-08 Feb-2010 Walz 2 Mary Ward-Callan * Adapted from Built to Last, Collins and Porras, 1994

3. Computer Society IEEE IEEE Strategies Standards Association CS SAB S2ESC TC on SE Feb-2010 Walz 3

4. S2ESC Mission • To develop and maintain a family of software and systems engineering standards that is authoritative, relevant, coherent, comprehensive, and effective in use by practitioners, organizations, and educators; • To aid the community in improving the quality of delivered software and systems containing software; • To support improvements in the effectiveness and efficiency of software and systems engineering processes; • To promote the profession of software and systems engineering, through products such as the Software Engineering Body of Knowledge and certification mechanisms for software engineering professionals; • To improve communications among stakeholders and suppliers of software and systems engineering services; • To develop supporting knowledge products that aid practitioners, organizations, and educators in understanding and applying our standards. Feb-2010 Walz 4 Jan 2008

5. S2ESC Planning History • July 2007 F2F spawn 8 teams  • but little progress  • Feb 2008 F2F agreed on S2ESC Mission • July 2008 F2F Minutes  Tactics • Fall 2008, Paul, David, Chuck, John • Split Mission into six Mission parts & parts into “Mission Attributes” • Mapped F2F Tactics to Mission Attributes • Articulated “Strategy” / Tactic; Reworked “Tactics” • Feb 2009, F2F • Members volunteered to their favorite Tactics  • Jul 2009, F2F • Determined S2ESC has sufficient “energy” (members + time) to carry through on the highest priority StrategyTactics combos => Top 3 Strategies determined  • LiveMeetings in August w/ absences  Feb-2010 Walz 5

6. Major Issues To Address • Developing a S2ESC standards roadmap showing future direction , commitment to grow the collection, and priorities for standards to be developed. This includes delineation of which are just adoptions of ISO Stds, and which are S2ESC innovations. • Developing a viable process/ mechanism for recruiting S2ESC and WG participants, and commitment to perform. Should include staff roles in this. • Developing a process/mechanism for increasing the visibility of S2ESC, and commitment to perform. Should include staff roles in this.

7. Approach • Divide into 2 teams to develop tactics for Items 1 & 2 • Brain storm • Report out to the group as a whole. • Commit to action.

8. Team 1: Roadmap Tasking • Identify target market needs • Identify areas of desired content for standards (12207/15288 processes, Service Mgt, IT Governance, Agile …) • Identify types of content (process descriptions, artifact guides, etc.) • Rank top priorities

9. Team 2: Recruiting Tasking • Brainstorm and rank best methods for recruiting qualified and committed volunteers to staff WGs

10. Process • Each team meets for an hour • John and Chuck to facilitate and record team decisions • Team to present to the group (1/2 hour each) • Discussion • Assignment of Action Items

11. Team 2: Recruiting Volunteers Team 1: Roadmap • Annette • Carl • Chuck • Jim • Paul • Pieter • Bob • John • Mark • Malia • Pam

12. Backup

13. Team 1: Roadmap • Annette • Carl • Chuck • Jim • Paul • Pieter

14. Team 2: Recruiting Volunteers • Bob • John • Mark • Malia • Pam

15. Tactics Owners 1B. Relevant: Establish an S2ESC standards evolution plan ("roadmap") showing future direction and commitment to grow 1B0. Mechanism to evision new standards / new areas, for tactics 1B1 & 1C1 Joe, John, Paul, 1B1.Look at stakeholder communities / practitioner conferences with growing interests and opportunities for standards development / SE Principles Joe, John, Paul, 1B2.Query our industry advisory boards: CS, TAB, SA, SE, Sectors, Mark, David P, John 1C. Integrated: Define the relationships of the standards within the S2ES collection. Assure cross-project coordination across S2ES WGs 1C1.Sketch out relationship of processes i.e. software support processes, new SWEBOK KA Jim, Chuck, Carl 1C2.MB work with WG Chair to insure Std integration from ExCom Project consistency requirements David 1C3.MB approval of Project consistency requirements and draft Std based on existing S2E P&P and Std relationships & WG coordination David 1C4.MB Repr report to MB Chair on WG coordination MB 1H. Authoritative Communications from S2ESC to the community: Communicate with software engineering sector decision makers to learn how to improve our standards evolution vision (roadmap) 1H1. Learn & capture issues from list below to work to conclusion: Lou, Paul, Jim, Tom Kurihara, Joe, John, •SEI advocates & process designers •PMI advocates & PMPs •INCOSE advocates •NDIA SW Industry Experts Panel •Portion of IEEE-SA CAG •Portion of IEEE-CS IAB (ATEF) •CSDP/CSDA COI/POI •SWEBOK Industry Advisory Board Strategies/Tactics selected Feb-2010