|
3 | 3 | <head> |
4 | 4 | <meta charset="utf-8" /> |
5 | 5 | <meta name="viewport" content="width=device-width, initial-scale=1" /> |
6 | | - <title>Method Timeline | LotusLift</title> |
7 | | - <meta name="description" content="Four-phase AI-assisted methodology for Lotus Notes modernization." /> |
| 6 | + <title>Method And Playbook | LotusLift</title> |
| 7 | + <meta name="description" content="Four-phase AI-assisted modernization method with executive summary and detailed execution playbook." /> |
8 | 8 | <link rel="preconnect" href="https://fonts.googleapis.com" /> |
9 | 9 | <link rel="preconnect" href="https://fonts.gstatic.com" crossorigin /> |
10 | 10 | <link |
|
21 | 21 | <nav> |
22 | 22 | <a href="index.html">Home</a> |
23 | 23 | <a href="method.html" aria-current="page">Method</a> |
24 | | - <a href="apps.html">Workstreams</a> |
| 24 | + <a href="workstreams.html">Workstreams</a> |
25 | 25 | <a href="security.html">Security</a> |
26 | 26 | <a href="copilot-tips.html">Tips</a> |
27 | 27 | </nav> |
@@ -151,20 +151,127 @@ <h2>Execute</h2> |
151 | 151 | <section class="method-divider reveal" aria-label="Full methodology divider"> |
152 | 152 | <p class="eyebrow">Detailed Reference</p> |
153 | 153 | <h2>Full Methodology</h2> |
154 | | - <p>The embedded reference below contains the complete step-by-step methodology, prompts, and time allocation.</p> |
| 154 | + <p>The detailed execution guide below extends the same method with inputs, steps, outputs, prompting patterns, and timeline.</p> |
155 | 155 | </section> |
156 | 156 |
|
157 | | - <section class="method-embed reveal delay-1" aria-label="Embedded full methodology"> |
158 | | - <iframe src="methodology.html" title="Full Methodology"></iframe> |
| 157 | + <section class="doc-content reveal delay-1" aria-label="Full methodology details"> |
| 158 | + <h2>Detailed Methodology</h2> |
159 | 159 | <p> |
160 | | - Prefer a dedicated page? |
161 | | - <a class="btn btn-primary" href="methodology.html">Open Full Methodology</a> |
| 160 | + This is the full execution playbook used by the team. It preserves the same four phases while making ownership, |
| 161 | + deliverables, and quality gates explicit. |
| 162 | + </p> |
| 163 | + |
| 164 | + <h3>Phase 1: Discover And Frame</h3> |
| 165 | + <p><strong>Goal:</strong> capture enough legacy context for accurate modernization planning.</p> |
| 166 | + <p><strong>Inputs:</strong> anonymized screenshots, schema metadata, business rules, and user-role context.</p> |
| 167 | + <p><strong>Process:</strong></p> |
| 168 | + <ol> |
| 169 | + <li>Collect and organize approved discovery artifacts.</li> |
| 170 | + <li>Use AI to draft structured documentation and workflow narratives.</li> |
| 171 | + <li>Run DTB review to correct assumptions and confirm fidelity.</li> |
| 172 | + </ol> |
| 173 | + <p><strong>Outputs:</strong> validated context package, workflow inventory, and baseline constraints.</p> |
| 174 | + |
| 175 | + <h3>Phase 2: Define Requirements</h3> |
| 176 | + <p><strong>Goal:</strong> translate discovery into implementation-ready requirements.</p> |
| 177 | + <p><strong>Process:</strong></p> |
| 178 | + <ol> |
| 179 | + <li>Generate draft functional requirements and user stories with AI.</li> |
| 180 | + <li>Prioritize scope with DTB stakeholders.</li> |
| 181 | + <li>Define non-functional expectations and acceptance criteria.</li> |
| 182 | + </ol> |
| 183 | + <p><strong>Outputs:</strong> prioritized requirements, user stories, and acceptance criteria.</p> |
| 184 | + |
| 185 | + <h3>Phase 3: Plan Conversion</h3> |
| 186 | + <p><strong>Goal:</strong> establish architecture, sequencing, and risk controls before coding.</p> |
| 187 | + <p><strong>Process:</strong></p> |
| 188 | + <ol> |
| 189 | + <li>Use AI to propose architecture options and conversion slices.</li> |
| 190 | + <li>Finalize technical decisions and migration sequencing with DTB leads.</li> |
| 191 | + <li>Define guardrails for data handling, quality, and release readiness.</li> |
| 192 | + </ol> |
| 193 | + <p><strong>Outputs:</strong> target architecture, conversion sequence, and risk-control plan.</p> |
| 194 | + |
| 195 | + <h3>Phase 4: Execute And Assure</h3> |
| 196 | + <p><strong>Goal:</strong> deliver modernization increments quickly without sacrificing quality.</p> |
| 197 | + <p><strong>Process:</strong></p> |
| 198 | + <ol> |
| 199 | + <li>Generate implementation increments using AI-assisted coding.</li> |
| 200 | + <li>Apply DTB-led reviews for correctness, maintainability, and security.</li> |
| 201 | + <li>Iterate with tests, refactoring, and documentation updates.</li> |
| 202 | + </ol> |
| 203 | + <p><strong>Outputs:</strong> working modernization increments, tests, and reusable delivery patterns.</p> |
| 204 | + |
| 205 | + <h3>Prompting Patterns By Phase</h3> |
| 206 | + <ul> |
| 207 | + <li><strong>Discover:</strong> summarize fields, entities, workflows, and validation assumptions from inputs.</li> |
| 208 | + <li><strong>Define:</strong> generate user stories and traceable acceptance criteria tied to business outcomes.</li> |
| 209 | + <li><strong>Plan:</strong> propose architecture alternatives and phased conversion plans with tradeoffs.</li> |
| 210 | + <li><strong>Execute:</strong> generate code/tests, then review/refine against quality and security controls.</li> |
| 211 | + </ul> |
| 212 | + |
| 213 | + <h3>Hackathon Timebox (7 Hours)</h3> |
| 214 | + <table> |
| 215 | + <thead> |
| 216 | + <tr> |
| 217 | + <th>Time</th> |
| 218 | + <th>Phase</th> |
| 219 | + <th>Activity</th> |
| 220 | + </tr> |
| 221 | + </thead> |
| 222 | + <tbody> |
| 223 | + <tr> |
| 224 | + <td>9:00-9:30</td> |
| 225 | + <td>Setup</td> |
| 226 | + <td>Introductions, environment readiness, and scope alignment</td> |
| 227 | + </tr> |
| 228 | + <tr> |
| 229 | + <td>9:30-10:30</td> |
| 230 | + <td>Phase 1</td> |
| 231 | + <td>Discovery capture and documentation synthesis</td> |
| 232 | + </tr> |
| 233 | + <tr> |
| 234 | + <td>10:30-11:00</td> |
| 235 | + <td>Phase 2</td> |
| 236 | + <td>Requirements definition and prioritization</td> |
| 237 | + </tr> |
| 238 | + <tr> |
| 239 | + <td>11:00-11:30</td> |
| 240 | + <td>Phase 3</td> |
| 241 | + <td>Conversion planning and architecture decisions</td> |
| 242 | + </tr> |
| 243 | + <tr> |
| 244 | + <td>11:30-12:00</td> |
| 245 | + <td>Break</td> |
| 246 | + <td>Lunch</td> |
| 247 | + </tr> |
| 248 | + <tr> |
| 249 | + <td>12:00-3:00</td> |
| 250 | + <td>Phase 4</td> |
| 251 | + <td>Execution sprint with AI-assisted coding and reviews</td> |
| 252 | + </tr> |
| 253 | + <tr> |
| 254 | + <td>3:00-3:30</td> |
| 255 | + <td>Demo</td> |
| 256 | + <td>Working increment walkthrough and outcomes review</td> |
| 257 | + </tr> |
| 258 | + <tr> |
| 259 | + <td>3:30-4:00</td> |
| 260 | + <td>Wrap-up</td> |
| 261 | + <td>Lessons learned, next steps, and enablement handoff</td> |
| 262 | + </tr> |
| 263 | + </tbody> |
| 264 | + </table> |
| 265 | + |
| 266 | + <p> |
| 267 | + Need the markdown source version? |
| 268 | + <a class="btn" href="methodology.html">Open Generated Methodology Page</a> |
162 | 269 | </p> |
163 | 270 | </section> |
164 | 271 | </main> |
165 | 272 |
|
166 | 273 | <footer class="layout footer"> |
167 | | - <p>Repeatable by design: discover, define, design, deliver.</p> |
| 274 | + <p>Repeatable by design: discover, define, plan, execute.</p> |
168 | 275 | </footer> |
169 | 276 |
|
170 | 277 | <script src="site.js"></script> |
|
0 commit comments