SWBPIPE · The open manual

Human–agent teams

Project Management for Human–Agent Teams

A practical manual

Ryan Tufts Version 7 Chirality AI Ltd · Calgary, Alberta
AuthorshipM

Authorship and preparation


I directed the preparation of this manual. Its main sources were my theses, my explanations of the method, and the practices developed in Chirality. I chose its purpose, readership, and philosophical approach. I also supplied examples of technical writing to establish the standard I wanted: sufficient explanation for readers to understand the method and put it to use.

ChatGPT wrote much of the text. It organised the material, drafted chapters, developed examples, proposed distinctions, and revised its work in response to my comments. Its contribution included developing the argument as well as putting it into words. It also checked passages against the supplied sources, identified inconsistencies, prepared the document formats, and kept editorial records.

We worked chiefly a chapter at a time. ChatGPT prepared a draft and identified questions or choices that needed my attention. I read it, corrected its meaning, supplied further material, and directed revisions. An early, shorter treatment was expanded where the reader needed more explanation. The drafts also helped me recognise and state ideas I had not yet explained clearly. Once the chapters were established, I asked the agent to consolidate the book and draft its concluding assessment. Later amendments still required review.

The method continued to develop during this work. As I clarified the project phases, the use of dependency graphs, the direction of continuing work, and the treatment of unfinished tasks, the affected chapters were revised. Some gaps required a separate design assignment. A missing procedure for preparing software requirements, for example, led me to ask ChatGPT to draft one using the existing design-basis practice and Chirality’s method for developing workflows. The result remained a proposal awaiting adoption and examination in use.

A separate Codex agent, familiar with the Chirality repository, reviewed the manuscript’s treatment of its operating practices. ChatGPT considered that review and revised the text. Further editing placed the general management explanations in this manual and the detailed repository procedures in the companion user manual.

Review covered the meaning of the terms, the sources supporting the claims, whether the instructions could be followed, and the reasons for each recommendation. The agents checked references, figures, and layout. I judged whether the text expressed the practice I intended to teach, and asked for examples or further explanation wherever it left too much for the reader to infer.

The division of responsibility was the one described throughout the book: the agents proposed and developed the text; I judged what to accept. Constructed examples illustrate the method, while reports from working projects support particular recommendations. The preparation of this book does not establish that every practice it describes has been proved effective. Readers must examine those recommendations against the conditions of their own work. Publication is my decision, and I am responsible for the text I approve.

ContentsM

Contents


    1. 1.1 An intended result and a reason to pursue it
    2. 1.2 Developing the intention with an agent
    3. 1.3 Objectives, constraints, and commitments
    4. 1.4 Useful work while the design remains open
    5. 1.5 Examining work received from an other
    6. 1.6 Establishing a basis that another participant can use
    7. 1.7 How the project's work changes as it develops
    8. 1.8 Organising the roles around the work
    9. 1.9 Responding when the work changes the basis
    10. 1.10 Carrying the undertaking through successive development sessions
    1. 2.1 Prepare a basis document that people can use
    2. 2.2 Establish what each source is allowed to support
    3. 2.3 Understand the product before selecting its document structure
    4. 2.4 Plan the sections, their sources, and their expected contents
    5. 2.5 Write requirements that preserve the intended distinctions
    6. 2.6 Preserve uncertainty and accepted change while writing clearly
    7. 2.7 Decide what can remain open through the next phase
    8. 2.8 Produce bounded contributions under a common plan
    9. 2.9 Review the authored document against its basis
    10. 2.10 Accept an identified document and preserve the work that remains
    11. 2.11 Carry the accepted basis into FEED
    12. 2.12 Maintain the relationship between the basis and later work
    1. 3.1 Establish the scope to be divided
    2. 3.2 Choose the Package boundaries
    3. 3.3 Define the Deliverables
    4. 3.4 Check coverage and accept the decomposition
    5. 3.5 Prepare the workspace
    6. 3.6 Write the deliverable scope of work
    7. 3.7 Establish evaluation and boundary ownership
    8. 3.8 Complete setup and begin execution definition
    9. 3.9 State the dependencies
    10. 3.10 Extract and examine the project graph
    11. 3.11 Resolve closely coupled work
    12. 3.12 Construct the DAG and complete the 30% phase
    1. 4.1 Steer the development undertaking
    2. 4.2 Construct and traverse a local work graph
    3. 4.3 Organise the agents and their execution resources
    4. 4.4 Develop the technical details
    5. 4.5 Commission a bounded contribution
    6. 4.6 Coordinate parallel work
    7. 4.7 Carry findings into decisions and change
    8. 4.8 Implement and exercise the result
    9. 4.9 Preserve the evidence of development
    10. 4.10 Review and integrate each contribution
    11. 4.11 Close the records and preserve continuation
    12. 4.12 Establish the route toward completion
    1. 5.1 Establish the completion undertaking
    2. 5.2 Sustain work over many assignments and sessions
    3. 5.3 Arrange parallel completion
    4. 5.4 Reduce the recurring cost of the loop
    5. 5.5 Read completion from the production contract
    6. 5.6 Manage the remaining obligations
    7. 5.7 Bring the contributions together
    8. 5.8 Close the records against the integrated result
    9. 5.9 Assemble the grounds for a completion judgment
    10. 5.10 Deal with late findings and changes
    11. 5.11 Establish the position at 90%
    12. 5.12 Examine the product in use
    13. 5.13 Debug the identified candidate
    14. 5.14 Prepare the product for the publication decision
    1. 6.1 Join the established delivery workflow
    2. 6.2 Preserve the identity of the delivered result
    3. 6.3 Transfer the continuing responsibilities
    4. 6.4 State the project’s outcome
    5. 6.5 Give subsequent work a sound starting point
    1. 7.1 Agency requires a common purpose
    2. 7.2 Progress changes the work that management must do
    3. 7.3 Keep the organisational choices few and the assignments precise
    4. 7.4 Make the record useful to thought and action
    5. 7.5 Optimise the whole course to an examined result
    6. 7.6 Judge the project by the product and the responsibility it leaves

The short form of this manual is the Field Book. Its companion for work in the Chirality repository is the Chirality Agent User Manual.

Project Management for Human–Agent Teams · published as written from Project_Management_for_Human_Agent_Teams_Consolidated_v7.md, Chirality repository revision 9ffc54afca

SWBPIPE, the open manual · The program: swbpipe.com · Chirality AI Ltd