If you’re considering “going agile,” one of the critical components of such a transformation will be adopting team structures. In your current, pre-teaming state, your developers are probably working by themselves, and may be engaging directly with stakeholders. Agile will place your developers into teams. Teaming is important, as it will enable your development staff to actively learn from one another, improving the quality of their individual and collective work, and improving the work environment.
It’s been a while since I’ve checked in on enterprise architecture (EA). My last in-depth work with EA was around 2011 when I was on detail to the Office of Personnel Management’s Open Government Team. The EA model I worked with was the top-down organizational design of information technology assets, data assets, and business processes. Many of you are probably familiar with this traditional EA model. Six years later, it is predicted that in 2018 that “half of enterprise architecture (EA) business architecture initiatives will focus on defining and enabling digital business platform strategies.
In March, the team of writers and editors at USAGov adopted some agile principles in an attempt to streamline our content development process. We hoped operating in a more agile manner would help us address some of the challenges we were facing as a team: Being asked to support many new projects Competing priorities Bottlenecks and silos It was a big change in the way we work. Our previous model had been based on a newsroom-style operation where people were clustered together around specific areas of content or “beats” to use the journalism terminology.
Along with the New Year comes new buzzwords. Here are some that you are certain to hear about and see this year. Chatbot Short for ”chat robot,” a chatbot is a computer program that simulates human conversation, or chat, through artificial intelligence. They are commonly found on web sites and used to communicate with a person—you might have seen them on shopping sites as a customer service assistant. One well known example of a chatbot is ALICE (short for Artificial Linguistic Computer Entity), an open source, natural language chatbot that relies on artificial intelligence for human interaction.
Some months ago, 18F started playing with kanban as a way to manage and improve our processes. (It turns out that “DO ALL THE THINGS!” was maybe not the best motto.) Kanban is a methodology that helps you to remove inefficiencies and reduce waste by visualizing workflow. It’s also used to balance capacity and demand by implementing a “pull system” and limiting the amount of work in progress. You don’t have to change anything when you first start to use it, you just put up a board, represent your current work process, put in some work limits, and start tracking what you’re doing and learning from it.
The agile transformation at the Census Bureau started several years ago after GAO recommended Census implement a standard Systems Development Lifecycle (SDLC). Around the same time came the newly released Digital Services Playbook as well as a general shift in the industry to using a more agile approach in software development to improve product delivery and business customer satisfaction. Along with the clear benefits, there was a general appetite from individuals and teams to introduce agile concepts into their project.
Armed with the knowledge that ‘most studies suggest that losses are twice as powerful, psychologically, as gains,’ federal change agents can better prepare for possible cultural resistance as they begin to implement agile practices at their agencies. There are a variety of resistant-to-change personas (change is painful for most of us, but we dislike it in different ways) those seeking change will need to understand to be successful. Bill Brantley, ‘agile OG,’ from the U.