Anyone who works in agile software development knows how important it is to have an issue tracker application. These applications show the issues your team has completed, is working on, and will be working on in the future.
For many teams, Jira is the issue tracker of choice. One of the perceived advantages of Jira is that it serves as a “single source of truth” across an organization. This gives managers an accurate view into the progress, or lack thereof, of an organization against its product development goals.
But is Jira, or any issue tracker application, suited to this role as single source of truth? Is Jira an anti-pattern; poised to attack us when our back is turned?
Alfresco is bringing their Alfresco Days series of events back to D.C. again on May 23. The 2019 Alfresco Government Summit focuses on generating discussions around leveraging Alfresco as a platform in the cloud. Specifically, as an open source content services platform living in AWS.
TeraThink will be there again this year to talk about how we make content services work using Alfresco in AWS. We have been leveraging the content services platform (CSP) approach to deploying enterprise content management (ECM) for a few years. During that time, we’ve learned a lot of lessons. We will be bringing that expertise to the Application Platform Revolution Panel moderated by Alfresco founder John Newton.
Before the 23rd, I want to take a few minutes to giving you a preview of some of the thoughts we will be sharing.
One of the great things about using content services in your digital transformation efforts is the automation a lot of information governance processes. You can link business entities, automate the application of policies, and reduce duplicate content. All of which increases reliability of information and reduces redundancy. The newly digitized processes streamline the work that you do daily, increasing your ability to innovate across your business.
Sounds great, right?
But what about those policies you are applying? Have you thought about what they are doing? Do they reflect the realities of your day-to-day? Now that you are no longer dealing with paper and information silos, you can revisit your records policies that were written years ago.
Do you suspect that your company’s commitment to agile consists of jargon and sloganeering, as opposed to actual organizational and cultural change? Then you would do well to refer to this pamphlet on Detecting Agile BS (pdf) produced by the Department of Defense’s (DoD) Defense Innovation Advisory Board (DIB) in October of 2018. The DIB established itself to bring the best practices and innovations of Silicon Valley to DoD software development. The pamphlet was the result of luminaries such as Eric Schmidt, Reid Hoffman, and Neil deGrasse Tyson coming together turning their gimlet eye towards true agile practices in DoD software development.
I’ve excerpted some interesting parts of the pamphlet below and tied in some of my perspectives based on my current TeraThink project at U.S. Citizenship and Immigration Services (USCIS). Full disclosure: TeraThink is a for-profit company, and as such is not 100%-free of BS. However, I like to think we have less BS than most. I’ll detail why through highlighting key flags that a projects is not truly agile.
We have been selected as the prime contractor by Pension Benefit Guaranty Corporation (PBGC) for their Financial Management Systems-Information Technology Support Services (FMS-ITSS) contract. This five-year unrestricted single award IDIQ (indefinite-delivery indefinite-quantity) contract, with a $100 million ceiling, represents exciting new work for TeraThink. The award demonstrates the continuing success of our strategy to lead transformation initiatives. We welcome the opportunity to support PBGC in achieving their strategic goals.
This time of the season always presents a good point to reflect on the past year; to take stock of key accomplishments and milestones while also looking to next year and the opportunities it presents.
For TeraThink’s ServiceNow practice, this has been an exciting year that has ushered in a number of client successes. It has also seen the addition of some great talent to our team and the establishment of our ServiceNow community of practice.
Today we are proud to announce that TeraThink has been awarded a $12M single award Task Order from the U.S. Department of Veterans Affairs. We will be performing independent verification and validation (IV&V) services in support of their Financial Management Business Transformation (FMBT) initiative. This multidimensional IV&V support for the VA’s financial business system implementation will utilize CGI’s Momentum® Federal ERP suite. This win demonstrates our long-held reputation for excellent performance delivering Enterprise Resource Planning (ERP) programs.
I’ve been speaking a lot about content services of late. At TeraThink, we are a big believer that good content services are a solid foundation for excellent user experience. This is why I’ve been focused on dispelling some of the hype around content services. One of the reasons I, and TeraThink, have been trying to push past the hype is because we are actively using content services to deliver solutions at scale.
Along the way, we’ve been trying to share some of our lessons. James Fintel shared what we’ve learned about building content services agilely using Kanban. What I wanted to share was some of our lessons on the delivery of content services to a government agency.
The U.S. Department of Agriculture (USDA) awarded TeraThink $10M for Organizational Change Management and Business Process Reengineering. Awarded as part of the USDA Shared Services Lines of Business Solutions (SSLOBS) Blanket Purchase Agreement (BPA), our expansive financial management and modernization experience is directly relevant to USDA objectives. This experience was key to our winning these task orders.
Here at Terathink, we are working with a large government agency constructing a content services platform. This platform allows content generated by benefit applications to be shared and reused across the organization’s disparate IT applications. We are doing this through the use of application programming interfaces, or APIs.
Our agile development team manages our work using a Kanban approach, from requirements gathering to the deployment of the API to a production environment. We have honed our use of Kanban to most effectively manage the work required to take a user request to functional reality.