Brian Fox is currently a management consultant at 18F at the General Services Administration (GSA). He has led Systems Development at U.S. Geological Survey (USGS) where he supervised development activity in support of The National Map. Brian also supported the National Geospatial-Intelligence Agency in a variety of roles, including joint military assignments in the United States and overseas. He holds an undergraduate degree in Geography from the University of Minnesota and a MBA from the University of Missouri - Saint Louis.
For those seeking ways to internally re-skill their workforce for digital transformation, a look at mythology reveals a recurring theme where those answering the call are involved in an iterative cycle of ‘leveling-up’, a theme that may help change-agents set conditions for successful retention and growth of organic digital talent.
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
It’s important for software development organizations to make it as easy as possible to enable improved stakeholder behavior. Development stakeholders can include business development representatives, product managers, and senior project managers, and they are typically carrying the weight of the organization’s mission. They are concerned about the organization’s goals, and are usually focused on ensuring