"Grow Your Own Project Know-how" Draft Protocol

Начать. Это бесплатно
или регистрация c помощью Вашего email-адреса
"Grow Your Own Project Know-how" Draft Protocol создатель Mind Map: "Grow Your Own Project Know-how"  Draft Protocol

1. Consolidate

1.1. Models of Your Know-how for Engaging Stakeholders

1.1.1. Revisit and update models of know how in Reflect, Survey, and Share stages based on current Experience

1.1.1.1. Root causes, Repertoire, Promising constructs, Career Map

1.1.1.1.1. Feed, have AI partner (same chat) regenerate Career Map for growing your know how

1.2. Approach to next project

1.2.1. ?and of the protocol your are using to grown and model it?

1.2.2. aligned with Career Map and informed by career coach

2. Share

2.1. Summary of Stage

2.2. Share Project Planning

2.2.1. With Team, Plan Constructs to Use.

2.3. Share Map

2.3.1. Identify SegmentsThat Could Assist Team

2.3.1.1. Desired

2.3.1.1.1. User Story

2.3.1.1.2. Product Backlog Grooming

2.3.1.1.3. User Story Workshop

2.3.1.1.4. Product Vision box Innovation Game

2.3.1.2. Acquired

2.3.1.2.1. Buy a Feature Innovation Game

2.3.1.2.2. User Interviews

2.3.2. Share Desired Know-how with Project Team

2.3.3. Offer to Leverage Constructs in Repertoire

2.3.3.1. Constructs in Repertoire

2.3.3.1.1. Buy a Feature Innovation Game

2.3.3.1.2. User Interviews

2.4. Share Project Work

2.4.1. Inform Career Coach re project team constructs, ask coach to tailor map of constructs dedicated to this project only

2.4.1.1. Tailor map to current project team context. prospective survey dedicated to learning and contributing project know-how in this project

2.4.1.1.1. From strategic map and current project plan, create personal project coach to support you in this project and team by the following steps.

2.4.2. Use constructs planned by team, Experience, Implement/do project

2.4.3. Get Coaching based on project map, ? Create? sidekick, job aid/performance support based on tailored map

2.4.3.1. Generate resources and plan for learning/performance support "advise" for growing constructs of dedicated map.

2.4.3.2. Coaching/personal advice

2.5. Join Team

2.5.1. Grok Current Team Constructs for Purpose, Perspective(s), KPI’s,

2.5.1.1. Current team has agile perspective on project work; key constructs, product vision, product vision box innovation game, user story, product backlog, sprint review, sprint retrospective

3. Map

3.1. ** Career Know-how for Engaging Stakeholders **

3.1.1. Develop Map

3.1.1.1. Relate Same Family Constructs by Complexity

3.1.1.2. feed families and constructs

3.1.1.3. structured as a tree with branches being families of related constructs

3.1.2. Surface family relationships among all key Constructs

3.1.3. incl. both

3.1.3.1. Model of current repertoire and prospective constructs

3.1.3.2. Constructs in repertoire and constructs in prospect

3.1.3.3. Constructs Aquired and Desired

3.1.4. Career map is sparse, high level, static model of your career know how for engaging stakeholders

3.1.4.1. Career Coach is a verbose, detailed, model of your know how at any given moment as well as a dynamic key resource for growing it furhter

3.1.4.1.1. Project Coach

4. Survey

4.1. Survey Key Global Constructs for Engaging Stakeholders

4.1.1. ID global consructs that seem promising for you (those that you are interested in now or may become interested in; promising constructs and similar

4.1.1.1. Feed Promising Constructs

4.1.1.1.1. Generate summary of promising construct features

4.1.1.1.2. Generate list of constructs similar to your promising constructs. Have chatbot Give a short name to each construct, followed by a one sentence explanation.

4.1.2. ID global constructs that are - for you - actionable(those you can leverage now or that you could probably learn to quickly

4.1.2.1. Feed Repertoire (name it for AI)

4.1.2.1.1. Generate global constructs for purpose similar to your repertoire. Have chatbot Give a short name to each construct, followed by a one sentence explanation.

4.1.3. ID global constructs that are - for you - comprehensible

4.1.3.1. Feed root causes (named for AI)

4.1.3.1.1. Generate summary

4.1.3.1.2. Generate a list of constructs that the global project community uses to address the root causes of failing to engage stakeholders (as you understand these causes). Have chatbot Give a short name to each construct, followed by a one sentence explanation.

4.2. Summary of Stage

4.3. Discover "Key" Global Constructs those that are Comprehensible, Actionable, and Promising for You

4.3.1. Feed both lists of constructs

4.3.1.1. Create a list of key constructs, those that will make up your strategic road map. Rank constructs of the list by both accessibility and vibrancy. Rank vibrant constructs over vibrant like. Prioritize constructs that appear both accessible and vibrant. List 30. Rank repertoire concepts over repertoire like.

4.3.1.1.1. Select cut off point or similar constructs

4.3.2. Build a list of key constructs for growing my own project know-how in engaging stakeholders

4.3.2.1. Build the list stepwise as set out in the steps below. Stop taking steps when the count of key constructs on the list is higher than the count of constructs in my repertoire by about 30 (+/- 2). As outputs at each step, first provide the count of constructs added in the step, then list the added constructs themselves, in bullet form, and then the complete list of constructs as of that step, also in bullet form.

4.3.2.1.1. Step 1 Add the constructs in my repertoire to the list of key constructs.

4.3.2.1.2. Step 2 add constructs that are promising, comprehensible, and actionable

4.3.2.1.3. Step 3 add constructs listed as promising and comprehensible or as promising and actionalble.

4.3.2.1.4. Step 4 add constructs listed either as promising and actionable or as actionable and comprehensible.

4.3.2.1.5. Step 5 add constructs listed only as comprehensible or only as actionable

5. Set Up

5.1. Preview Protocol

5.1.1. cycle as a whole

5.1.1.1. map and chatbot resources by phase

5.1.2. example of protocol use

5.2. Set Up Mindmeister

5.2.1. map is sparse, high level, static model of your know how and of the protocol your are using to grown and model it

5.2.1.1. conversation is a verbose, detailed, model of your know how at any given moment as well as a dynamic key resource for growing it furhter

5.2.2. from the template here, open a map in your Mindmeister platform.

5.3. Set Up Chatbot

5.3.1. Selection criteria

5.3.2. Configuration

5.3.2.1. single new chat

5.3.2.2. My Project Know-how for Engaging Stakeholders

5.3.2.3. CL AI?

5.3.2.4. Motivation and characterization

5.3.2.5. draft initial prompt to chatbot

5.3.2.5.1. connect to sources selected by CL and to internet

5.3.3. connection to rest of set up

5.3.3.1. steps here should be one time only

6. Experience

6.1. Steps

6.2. To begin growing your know-how in engaging stakeholders, select a team project that you have done, one that did very well and/or very badly at engaging lstakehoders.

6.2.1. Selected Done Project

6.3. Recall your experience in the Done Porject

6.3.1. Note plans, actions, outputs, and outcomes

6.4. For this Experience stage, note only done one you have selected

7. Reflect

7.1. Steps

7.2. Model Root Causes of Failure in done project

7.2.1. Career Root Cause Analysis

7.2.1.1. Failure to Engage Stakeholders

7.2.1.1.1. Root Cause Analsis

7.3. Model Repertoire of Project Know-how

7.3.1. Career Repertoire

7.4. ID **Constructs** that Worked in Done Project

7.5. MOdel Promising Constructs

7.5.1. Promising Constructs

7.6. List all **Contructs** that Worked in All Your Experience

8. Each verb here is the main activity in a given stage of this protocol for mapping project know-how. Direct object of all the verbs here is Project knowhow rfor Engagin Stakehoders

9. Use protocol starting at Share Stage instead of Set Up, You'll have