Json data for agile methodology visualization

agile.json

{
    "name": "Process",
    "title": "Our agile process", 
    "description": "We build properly tested software in short increments with constant feedback with our clients. Each development iteration delivers a more tested and documented product.",
    "children": [
        {
            "name": "Plan",
            "icon": "fa fa-magic fa-lg",
            "description": "Our planning process translates the business needs of your project into clear requirements. We listen, research and collaborate with you to deliver fully informed project requirements.",
            "order": 1,
            "size": 1000,
            "children": [
                {
                    "name": "Research",
                    "icon": "fa fa-binoculars fs-lg",
                    "description": "Our discovery process helps define how YOU will measure the success of your project. We guide you through a series of tasks to define users, goals and content needs until we have full clarity on what you want your application to accomplish.",
                    "size": 1000,
                    "order": 1
                },
                {
                    "name": "Requirements",
                    "icon": "fa fa-gears fa-lg",
                    "class": "btn-process large",
                    "title": "Requirements",
                    "description": "While collecting requirements we begin planning how to build the application. We think through everything from the application's hosting needs to determining which pre-existing tools can be used versus created from scratch.",
                    "size": 1000,
                    "order": 2
                },
                {
                    "name": "Prototype",
                    "icon": "fa fa-paper-plane fa-lg",
                    "description": "For some projects, an initial prototype can be programmed. They are a simple visualization with no color, logos or fonts of how the application will work when it is functioning",
                    "size": 1000,
                    "order": 3
                }
            ]
        },
        {
            "name": "Build",
            "icon": "fa fa-cubes fa-lg",
            "order": 2,
            "size": 3000,
            "description": "We apply the highest standards of quality control to every line of code we write. We pride ourselves on regular deployment, rigorous testing, documentation and transparency.",
            "children": [
                {
                    "name": "Roadmap",
                    "icon": "fa fa-road fa-lg",
                    "title": "Development Roadmap",
                    "description": "Once every application feature is defined and your project’s requirements are as efficient as they can be, every milestone is set with a clear timeline for completion.",
                    "size": 1000,
                    "order": 1
                },
                {
                    "name": "Prototype",
                    "icon": "fa fa-paper-plane fa-lg",
                    "description": "There's always more than one possible route. By quickly exploring a range of ideas we can agree on a direction that makes the most sense for your project.",
                    "size": 1000,
                    "order": 2
                },
                {
                    "name": "Develop",
                    "icon": "fa fa-desktop fa-lg",
                    "size": 3000,
                    "order": 3,
                    "description": "We are agile, we deploy functioning code often. From the start of the project, clients have access to our code and issue trackers. This workflow assures that only high-quality functioning code is ever pushed to production, and the client is always aware of our progress."
                },
                {
                    "name": "Test",
                    "icon": "fa fa-cogs fa-lg",
                    "size": 1000,
                    "order": 4,
                    "description": "Unit testing ensures that we catch potential errors before they are pushed to production. Though this seemed like a slower process up front, it saved invaluable time by avoiding errors of unknown origin on the live application."
                }
            ]
        },
        {
            "name": "Test",
            "title": "Client Testing",
            "icon": "fa fa-users fa-lg",
            "description": "At each iteration in our deployment cycle, You have the final say on whether the new features or bug fixes are suitable for deployment into the live application.",
            "size": 1000,
            "order": 3,
            "children": [
                {
                    "name": "Accepted",
                    "icon": "fa fa-thumbs-up fa-lg",
                    "order": 1,
                    "children": [
                        {
                            "name": "Testing",
                            "title": "System Testing",
                            "size": 1000,
                            "order": 1,
                            "description": "Depending on the architecture chosen, system testing can be complex endeavor which is a critical aspect of the software development lifecycle."
                        },
                        {
                            "name": "Release",
                            "size": 1000,
                            "order": 2,
                            "description": "One system testing is passed we deploy a new Release of your application. This can happen on a weekly basis."
                        },
                        {
                            "name": "Discuss",
                            "title": "Discuss new Features",
                            "size": 1000,
                            "order": 3,
                            "description": "After each deployment into the live application we can discuss with you new features or simply continue the development process following the Roadmap."
                        }
                    ]
                },
                {
                    "name": "Declined",
                    "icon": "fa fa-thumbs-down fa-lg",
                    "class": "btn-danger",
                    "title": "Client does not accept features",
                    "description": "In the unlikely event when You don't approve a set of new features, for whatever reason, we will listen to your concerns and act accordingly.",
                    "order": 2,
                    "children": [
                        {
                            "name": "Discuss",
                            "title": "Discuss Changes",
                            "size": 1000,
                            "order": 1,
                            "description": "When you don't approve a new feature we will sit down with you and discuss the changes. Because of our agile development cycle these changes are likely to be small."
                        },
                        {
                            "name": "Changes",
                            "title": "Apply changes",
                            "size": 1000,
                            "order": 2,
                            "description": "Back to the drawing board and apply the changes discussed"
                        }
                    ]
                }
            ]
        },
        {
            "name": "Support",
            "icon": "fa fa-star fa-lg",
            "description": "The most successful projects constantly improve over time. We offer a variety of support packages to suit every need and requirement.",
            "order": 4,
            "size": 2000
        }
    ]
}