To aggregate disparate developer tools and workflows.
A hole in the developer tool market plus high-level feature goals dictated that a new engineering pipeline and aggregation application be developed.
Goals such as associating reviews, builds and test results to commits, implied a total impact on every level of development including management and all the way to deployment.
Areas of work: Interactive Design, HTML/5, CSS/3 extended by SCSS, Keynote Wireframing, Rapid Prototyping in HTML
- Workflow Pipeline
- Aggregate disparate tools
- Traceability and Associations of other tools
Developers jump in and out of dozens of tools and processes throughout their workflow in order to do their job. A project pipeline tool to visualize disparate types of workflow information is needed.
Finding the common items being exported from the APIs was the defining moment for building true information flow, sharing common data and allowed for the shared visual language needed to aggregate and associate all other related pieces of data.
Knowing how the tools were distributed was instrumental in visualizing how the information might be displayed. It also forced me to gain an understanding of how these tools interconnected, why they were used, how they were used, why some features were more important than others and when we needed specific data and when to serve it up.
documentation and UI library:
Being the only UX person at CollabNet, means that my job doesn’t end when the product is ready for deployment. A number of documents and countless libraries must be collected and/or created to be truly ready for product launch.
Orchestrate version 1.0 available now!
- Control Center for Delivery Pipelines: creates traceability across disparate tools, enabling graphical traceability of delivery pipelines across tools and clouds to measurably reduce cycle times.
- Social Activity Streams: embedded social activity streams link comments and discussions to events, data and activities to provide context through continuous integration and continuous delivery pipelines.
- Agent-based APIs: an easy-to-use integration model provides traceability links between TeamForge and third-party tools. This eliminates "vendor lock-in." Pre-packaged integrations include Git and Subversion, Jenkins, TeamCity, ReviewBoard and others. This tool ecosystem can be expanded with community-built integrations.
Check out the Orchestrate Examples on YouTube here!
What we threw away:
When working in a scrum team, lots of ideas get thrown around, blue-sky approaches become experiments and mockups become prototypes. All in the name of progressing forward. But, alas, some things were never meant to be.