Archives page

Posts Tagged ‘CIO’

Part I: Implementing Agile at USCIS with Josh Seckel, Chief, ATD, USCIS

We’ve also got to create a culture of partnership. We recognize companies are in business to make money, but we’ve got to create alignment towards a bigger purpose – like changing the way federal IT works.

Sara Kindsfater-Yerkes, Chair of the GTSC Business Development Exchange, was able to sit down with Josh Seckel, Chief of the Applied Technology Division (ATD) at USCIS. In this two-part interview, they discuss the agile transformation at U.S. Citizenship & Immigration Services at the U.S. Department of Homeland Security. Among ATD’s chief responsibilities are driving the adoption of agile across the USCIS enterprise, brought about in part by providing agile coaching services – experts across the technical, process and organizational change domains who help clients shift their culture and mindset to lean/agile thinking. This is a sea change in Federal IT – moving away from the lengthy, and staged waterfall methods to continuous activities for developing software. By doing them continuously quality improves because testing starts day one, visibility improves through collaboration and increased visibility, and risk is reduced through continuous feedback and prioritization of work.  

GTSC: So Josh, we’ve known each other for a while now, but I’d like to give people insight into your background. Where should we start?

Josh: Where to start? So the dinosaurs roamed. No, just kidding! The short version is that after getting my Computer Science degree I went to work for IBM and got to participate in all aspects of the software development process – but come 2001 I was still programming in Cobol. I decided to go back to school and get my MBA which obviously taught be a great deal about the business-side of organizations. I get accounting, P&L, all that good stuff. After that, I came to DC and worked for a few federal contractors, which gave me the experience to support programs with the United States Marine Corps, the Joint Strike Fighter, the Domestic Nuclear Detection Office where I was part of a team introducing agile concepts and then to the Homeland Security Information Network coaching on agile. Then I came to USCIS, as a government employee. I’ve been around DHS since it’s inception and working with agile concepts like rapid application development before agile became mainstream.

GTSC: What has your role been at USCIS?

Josh: I came to USCIS to help CIO Mark Schwartz advise the organization on the adoption of agile and to be a federal coaching leading contractor coaches.

GTSC: What made the job as a “Govie” appealing to you?

Josh: The ability to say “yes” enticed me. I’d worked as a contractor and was told “great idea, but no” and wanted to listen to great ideas from both government and industry and be able to say “yes – let’s try that.” I also wanted the opportunity to really execute on this idea of agile adoption and improving federal IT more fully.

GTSC: You’ve been very mission focused from that perspective. Very cool. Your response made me think, and this a bit tangential, about the fed/contractor relationship. How do we change and improve that dynamic?

Josh: Good question. The government needs to do its part – we need to improve federal employee education and what I mean by that is putting someone in charge of overseeing an agile program with skills and experience in agile. We hire contractors because they have specific expertise that we don’t, but then we get unfriendly because they know things we don’t. The flipside of that is the perceptions that contractors think the government employees don’t know anything and that too causes tension.

GTSC: It’s definitely a vicious cycle that we’ve got to collectively break. There’s nothing more gratifying as a consultant then to work with a customer who needs your expertise and allows you to work with them to solve real problems.

Josh: Yes, so we’ve also got to create a culture of partnership. We recognize companies are in business to make money, but we’ve got to create alignment towards a bigger purpose – like changing the way federal IT works.

GTSC: You’ve been spearheading agile coaching internally at USCIS, what’s the value agile coaches provide? How are they different from Scrum Masters?

Josh: Well, I would start by saying that they don’t necessarily have to be different then scrum masters; really good, experienced scrum masters can be coaches. Agile coaches provide knowledge on how to do this new thing through their experiences not a 2-day course. Good coaches offer a broader perspective and are a good mirror – they are a reflection of the team back to itself, an objective 3rd party reflection. And they not only coach the development team, they coach management too.

STAY TUNED to next week when Sara and Josh discuss being a good “mirror,” coaches versus scrum masters, and how agile is driving culture change in the government.

Sara Kindsfater YerkesSara Kindsfater-Yerkes, leader of GTSC’s DHS Business Development Exchange and member since 2012, is an Organizational Change Strategist with expertise in guiding large-scale transformations, Sara is passionate about helping individuals and teams to become high performing and creating cultures in which all can thrive. She currently supports Josh and USCIS in the cultural adoption of lean/agile practices.

 

 

5/1 Federal Biometrics: Understanding USCIS with Leslie Hope

Biometrics is changing the way law enforcement and agencies that must track, identifiy and authenticate users aproach security.  The Department of Homeland Security’s Homeland Security Department’s U.S. Citizenship and Immigration Services biometric capture services at over 130 application support centers across the country. Biometrics are used to  process U.S. citizenship applications and immigration benefits applications.

USCIS collects photographs, digital fingerprints, passport scans, driver’s license scans, signatures, and other biometrics data from applicants. This information is used by the USCIS to determine qualifications for immigration benefits. The data is also used to conduct criminal background checks, which are required for the processing of many immigration benefits.

REGISTER 

 

Leslie Hope
Chief
DHS/UCCIS/ESD/Biometrics Division

 

About Leslie Hope
Leslie Hope is Chief of the Biometrics Division at U.S. Citizenship and Immigration Services (USCIS), a component of the Department of Homeland Security.  Ms. Hope serves as program manager and business owner for all biometric systems at USCIS and manages 137 Application Support Centers (ASCs) across the United States. ASCs allow applicants seeking an immigration benefit to submit biometrics to establish identity and to assist USCIS in determining eligibility with a background check. The results of background checks are disseminated for adjudication to USCIS operational directorates across the United States.  Ms. Hope has over 20 years’ experience supporting DHS in a variety of roles; to include acting CIO and Deputy CIO for many years.  Prior to joining the government Ms. Hope spent 15 years managing technology in the banking and airline industries.

 

Essential Steps to Prioritizing IT expenditures

More and more Federal CIOs (and their staffs) are realizing a need to get their arms around their in-house IT requirements vetting.  Since joining ISS in 2013, we have expanded our IT/Data requirements support at NOAA (National Ocean Service and National Weather Service) and Defense Logistics Agency (built and automated the “IT Front Door”).  We’ve been able to support various levels of requirements automation and sophistication.  Bottom line – we’ve had to serve the client’s mission to get a handle on what’s in their enterprise, and how to efficiently fill new requirements.

We’ve seen our clients realize that when a small agency becomes an enterprise, tools become capability suites and discussions become corporate communications.  It happens when the Office of the Chief Information Officer (OCIO) realizes they’ve lost visibility over new IT spending for tools, technologies or capabilities, or when the integration and sustainment costs are growing out of control.  CIOs need a structured, disciplined review and analysis of new and existing IT investments and capabilities, and they long for standard, repeatable processes.  But where do you start?

There are several essential steps when trying to manage your “approval life cycle” and better prioritize IT expenditures:

  • Provide a single face to the internal customer concerning new capabilities and requirements. That person or office receives reviews, coordinates and tracks requests through a matrixed team of subject matter experts across the organization.
  • Define the roles and responsibilities of each party in the process, and clarify the rules and policies that make the IT requirements vetting process mandatory.
  • Establish evaluation and approval criteria, business rules, quality checks and feedback reporting for requirement submissions (business case and life cycle analysis).
  • Build a knowledge base of existing tools and licenses. Accelerate the approval process when the desired capability exists within current IT solutions or systems.
  • Check requests against Chief Information Officer (CIO) and Chief Technology Officer (CTO) strategies, ensuring correct vetting, and documenting approvals.
  • Advertise capabilities and approvals to leadership, internal customers, and stakeholders.
  • Document architecture/configuration changes.
  • Establish linkages to the budget process where business cases can be vetted.

A skeleton view of a requirements review process has three essential phases, which we have seen broken into more, but rarely fewer steps:

Coherent Requirement Documentation – Every internal request for IT capability (resource dedication) should be approved by a business process owner before submittal.  This will help ensure both the clarity and completeness of the request.  Once a request is submitted, it should be reviewed by the requirements process owner to ensure it makes sense to the IT subject matter experts (SMEs) who can help translate the request from business process to technology/tool/process definition.  Once the analysts and the customers agree that they have accurately captured the essence of the need, the request moves forward to internal vetting and analysis.

Internal Vetting and Analysis – This is the most extensive step because it involves due diligence – ensuring the request improves either business operations or customer interface.  Analysts will first check the existing library of technologies and tools to ensure this need can’t be covered by an existing (or planned) capability.  If the need can be met with an existing technology or tool, the approval process can be accelerated.

Next the analysts work with the Chief Technology Officer to check for existing commercial-off-the-shelf (COTS) or government-off-the-shelf (GOTS) tools to fill the need.  If there are no existing tools, the CTO may need to help draft documentation to guide a developmental effort, which can reflect a significant time and resource commitment for the organization.

Finally, the analysts assess the relevance to the CIO/CTO strategies, compatibility with existing architectures, and the time/money required to move forward.  Once these issues are assessed, the request may be returned to the customer for adjustment/re-work, or forwarded for approval and funding.

Approval and Funding – When the team decides there is sufficient information and analysis to merit a decision, they recommend an approval level (based on resource commitment authorities).  For inexpensive efforts, this could mean an approval notice which authorizes the customer to buy the COTS/GOTS tool using office funds.  For more complex and expensive efforts, it may mean assigning a priority for resource competition at budget deliberation time.

The complexity of the mission, organization and supported processes will drive the complexity of the requirements approval process.  But once it’s in place, a structured, disciplined review and analysis of new and existing IT investments and capabilities using standard and repeatable processes will help prevent redundancy, prioritize investments, ensure architectural integrity and reduce life cycle costs.

Implementation – Integrated Systems Solutions has been developing a variety of requirements management systems for federal customers since 2008. Whether it’s IT requirements, IT modernization, environmental observation requirements, ocean observation requirements, or data/metadata requirements, we have experts who can guide you to a user-friendly, enduring solution.  We can match the sophistication and automation of your process (from hands-on committee-based discussions to end-to-end web-based solutions) based on your organizational needs, culture, time and fiscal resources.

Bob Ranck_picBrigadier General Bob Ranck (ret.) is Vice President of Integrated Systems Solutions (ISS), a Service-Disabled, Veteran-Owned Small Business (SDVOSB) possessing a Top Secret Facility clearance and ISO 9001:2008 certification.   General Ranck served as Director, Warfighter Systems Integration, Office of Information Dominance and Chief Information Officer, Office of the Secretary of the Air Force, the Pentagon, Washington, D.C.

Luke J. McCormack to serve as the DHS CIO

The following message is from DHS Acting Under Secretary for Management Chris Cummiskey:

I am pleased to announce that President Obama has appointed Luke J. McCormack to serve as the Department’s Chief Information Officer.  Mr. McCormack currently serves as the Deputy Assistant Attorney General for Information Resources Management/Chief Information Officer (CIO) at the Department of Justice, a position he has held since 2012.

Luke-McCormackPrior to this position, Mr. McCormack served in a variety of positions at DHS.  From 2005 to 2012, he served as the CIO for the U.S. Immigration and Customs Enforcement.  He served at Customs and Border Protection as Acting Director of Infrastructure Services Division from 2004 to 2005, Director of Architecture and Engineering from 2002 to 2003, and Director of Systems Engineering from 1999 to 2002.  Before joining the federal government, he served at various private sector companies including MCI and Ford Aerospace.  He received an M.B.A. from the Smith School of Business at the University of Maryland.

Mr. McCormack will oversee the Department’s continuing efforts to implement information technology (IT) enhancements and enhance IT security.

Mr. McCormack’s bio:

Luke J. McCormack will serve as the chief information officer (CIO) for the Department of Homeland Security (DHS). Prior to joining DHS, Mr. McCormack served as the ICE CIO since 2005 and was named CIO of the Department of Justice in February 2012. As the agency’s top technology administrator, Mr. McCormack brings significant management expertise from a career in both government and the private sector.

Mr. McCormack has more than 18 years of service in the federal government. Before joining ICE, Mr. McCormack served as acting executive director of the Infrastructure Services Division in the Office of Information Technology at U.S. Customs and Border Protection. In addition, he gained diverse experience in the private sector with MCI, Ford Aerospace and smaller minority-owned firms.

Since joining ICE, he has restructured the Office of the Chief Information Officer (OCIO) to ensure that it is aligned with the overall ICE mission, current operational priorities, core business processes and emerging information technology needs. He continually seeks opportunities to partner with other organizations within ICE, the Department of Homeland Security and other federal law enforcement agencies to provide support to operations and strategic initiatives.

Mr. McCormack holds a Masters of Business Administration degree from the University of Maryland, College Park, along with key certifications from the Columbia University Graduate School of Business, Customs Leadership Institute and the National Defense University.

A native of Long Island, N.Y., Mr. McCormack has two sons and resides in Virginia.

 

Key Cybersecurity Issues for Government Contractors

Dickstein Shapiro LLP and the Government Technology & Services Coalition (GTSC) held a webcast, “Key Cybersecurity Issues for Government Contractors.” This interactive program, of particular interest to government contractor compliance officers, CIOs, CISOs, General Counsel, and any other C-suite members, discussed how the federal government is planning on fundamentally altering its acquisition policies to make the cybersecurity of its contractors a top priority.

The discussion included:
– Proposed Federal Acquisitions Regulation (FAR) changes relating to President Obama’s Cybersecurity Executive Order;
– Planned changes to procurement requirements based on independent agency actions;
– Congressionally mandated cybersecurity requirements; and
Ways contractors can prepare for these changes

Speakers included:

Brian Finch, Partner, Global Security, Dickstein Shapiro LLP

Justin Chiarodo, Partner, Government Contracts, Dickstein Shapiro LLP

Emile Monette, Senior Action Officer for Cyber Security Policy, Government Services Administration

Kristina Tanasichuk, CEO, Government Technology & Services Coalition

View the slides here or watch the webinar by clicking the link below.

Screen Shot 2013-10-09 at 2.21.39 PM