{
    "document_id": 14132,
    "page": 14,
    "width_pt": 612,
    "height_pt": 792,
    "rotation": 0,
    "pipeline_version": "paddleocr-vl-1.6+paul-48",
    "engine": "paddleocr_vl",
    "source_run_id": 14245,
    "item_count": 11,
    "counts_by_type": {
        "footer": 2,
        "heading": 1,
        "link": 1,
        "list": 1,
        "list_item": 4,
        "text": 2
    },
    "build_ms": 1,
    "items": [
        {
            "id": "p14.1",
            "order": 1,
            "type": "heading",
            "bbox": {
                "l": 60.96,
                "t": 757.2,
                "r": 348,
                "b": 742.56
            },
            "text": "Using Agile to Supplement the Design Thinking Process",
            "attrs": {
                "block_label": "paragraph_title"
            },
            "level": 3
        },
        {
            "id": "p14.2",
            "order": 2,
            "type": "text",
            "bbox": {
                "l": 60.24,
                "t": 738.24,
                "r": 578.16,
                "b": 666.24
            },
            "text": "Design Thinking is especially valuable for the definition of problems and generating initial potential solutions (i.e. the ideation mode), but it does not fully address the problem of how to manage the prototype and test modes. Although it is generated from the software development world, the Agile Manifesto can be used to organize diverse, cross-functional teams to incrementally create solutions to complex problems. The Agile Manifesto (http://agilemanifesto.org) describes",
            "children": [
                {
                    "id": "p14.2.1",
                    "order": 3,
                    "type": "link",
                    "bbox": {
                        "l": 261.934,
                        "t": 681.674,
                        "r": 394.1,
                        "b": 667.25
                    },
                    "text": "(http://agilemanifesto.org)",
                    "attrs": {
                        "uri": "http://agilemanifesto.org",
                        "action_type": "/URI"
                    }
                }
            ]
        },
        {
            "id": "p14.3",
            "order": 4,
            "type": "list",
            "bbox": {
                "l": 80.64,
                "t": 658.274,
                "r": 369.84,
                "b": 588.96
            },
            "text": "",
            "attrs": {
                "item_count": 4
            },
            "children": [
                {
                    "id": "p14.3.1",
                    "order": 5,
                    "type": "list_item",
                    "bbox": {
                        "l": 80.64,
                        "t": 658.274,
                        "r": 361.44,
                        "b": 643.85
                    },
                    "text": "individuals and interactions over processes and tools",
                    "marker": "•"
                },
                {
                    "id": "p14.3.2",
                    "order": 6,
                    "type": "list_item",
                    "bbox": {
                        "l": 80.64,
                        "t": 640.274,
                        "r": 369.84,
                        "b": 625.44
                    },
                    "text": "working software over comprehensive documentation",
                    "marker": "•"
                },
                {
                    "id": "p14.3.3",
                    "order": 7,
                    "type": "list_item",
                    "bbox": {
                        "l": 80.88,
                        "t": 622.274,
                        "r": 344.64,
                        "b": 607.85
                    },
                    "text": "customer collaboration over contract negotiation"
                },
                {
                    "id": "p14.3.4",
                    "order": 8,
                    "type": "list_item",
                    "bbox": {
                        "l": 80.88,
                        "t": 604.274,
                        "r": 315.6,
                        "b": 588.96
                    },
                    "text": "responding to change over following a plan",
                    "marker": "•"
                }
            ]
        },
        {
            "id": "p14.4",
            "order": 9,
            "type": "text",
            "bbox": {
                "l": 60.24,
                "t": 574.32,
                "r": 578.16,
                "b": 488.16
            },
            "text": "The first, third, and fourth points have clear implications for student teams working with those outside the academy. Introducing students to these principles through the new Humanics sequence and having it culminate in the capstone project will allow students to keep learn the collaborative aspect of Design Thinking. Students will also be reminded by the capstone project that although they will go into a project with a sense of direction, that direction may need to change once other factors are uncovered during the search for the best solution to a problem."
        },
        {
            "id": "p14.5",
            "order": 10,
            "type": "footer",
            "bbox": {
                "l": 36,
                "t": 36.48,
                "r": 49.44,
                "b": 24.96
            },
            "text": "10",
            "attrs": {
                "block_label": "number"
            }
        },
        {
            "id": "p14.6",
            "order": 11,
            "type": "footer",
            "bbox": {
                "l": 322.08,
                "t": 37.44,
                "r": 576.96,
                "b": 23.76
            },
            "text": "Quality Enhancement Plan: “Learning that Works”",
            "attrs": {
                "block_label": "footer"
            }
        }
    ],
    "excluded_furniture": {
        "first": [],
        "last": []
    }
}