• Liked Richard Cheng
    keyboard_arrow_down

    Agile at the Office of Personnel Management: The USAJOBS Product Owner's Perspective

    Richard Cheng
    Richard Cheng
    schedule 2 years ago
    Sold Out!
    60 mins
    Talk
    Beginner

    The USAJOBS program was a highly visible, time sensitive program, with potentially high government dollar value. To effectively execute the project, the USAJOBS program decided on an Agile approach and in this approach, government program managers were identified to be Agile Product Owners. This session features the experiences, thoughts, and challenges facing the Agile Product Owners on USAJOBS. Key thoughts from this session include:

     

    1. The differences between Project Management and Product Management 

    2. Shifting from big up front planning to responsible up front planning combined with just in time planning 

    3. Managing Product Owner bandwidth expectations 

    4. The impact of Agile from a Product Owners view

     

    The session is hosted by the former USAJOBS Product Owner along with an Agile Coach.  The session will explore Product Ownership and Agility on Federal Programs.

    Bios:

    Alesia Booth grew up in Federal human resources - her first job was with the National Institutes of Health payroll office at 16 years old. Since then, she's managed websites, document libraries, corporate recruitment programs, staffing systems and hiring reform process change management activities. Which is she ended up at USAJOBS. Since then, Alesia moved to Department of the Treasury to be the program manager of the HR Line of Business CareerConnector product for classification and staffing. At Treasury, she continues concentrate on solving multiple agency recruitment challenges to bring the best and brightest talent into the Federal workforce. Additionally, she worked with Treasury Enterprise Business Solutions as a champion of Agile development and recruitment data standardization Government-wide. Alesia is now back at OPM leading OPM's USAStaffing efforts.

     

    Richard Cheng, Principal Consultant at Excella Consulting, provides consulting services to commercial and federal clients in the Washington, DC area. Richard coaches, mentors, and trains clients on understanding and implementing Agile and Scrum. He also leads Excella’s Agile Center of Excellence.  A graduate of Virginia Tech, Richard has authored several publications on project management, presented at Agile and PMI sponsored industry events, is a member of Mensa, and holds certifications including Certified Scrum Training (CST), Certified Scrum Master (CSM), Certified Scrum Product Owner (CSPO), Certified Scrum Professional (CSP), PMI Agile Certified Practitioner (PMI-ACP) and Project Management Professional (PMP).  Richard is a founder and on the executive committee of the Agile Defense Adoption Proponents Team (ADAPT).

  • Liked Shawn Faunce
    keyboard_arrow_down

    Engaging a Product Owner on a Government Contract: Challenges and Solutions

    Shawn Faunce
    Shawn Faunce
    schedule 2 years ago
    Sold Out!
    30 mins
    Talk
    Beginner

    Great systems require active, capable Product Owners.  Functional innovation is not possible without their commitment and involvement in the project.  Too often in government contracting, the Product Owner is an Absentee Owner.  Agile Development teams often seek out tools and techniques to create great systems, however too frequently what is holding them back is the lack of an engaged Product Owner. Teams in this situation must face the elephant in the room if they desire to build a system that brings positive change in efficiency, productivity, quality, usefulness, and adoption.  This talk shares solutions I have used for challenges I see again and again on government contracts.

    The talk begins with some introductory material on the problem, its causes, what I mean by functional innovation, and why this is required to build great systems.  I describe four challenges with Product Owner engagement that are not unique to government contracting, but that I see recurring on projects: committing staff, procurement practices, role ambiguity, and absentee ownership.

  • Liked Aaron Pava
    keyboard_arrow_down

    Agile Gov Playbook: Dissecting the New White House TechFAR Handbook

    Aaron Pava
    Aaron Pava
    schedule 2 years ago
    Sold Out!
    30 mins
    Talk
    Intermediate

    The White House recently created a new Government Digital Services group to deliver “customer-focused government through smarter IT.” As part of this announcement the Office of Management and Budget released the “Digital Services Playbook” and an accompanying “TechFAR Handbook for Procuring Digital Services Using Agile Processes” to make it easier for agencies to procure and implement agile.


    In this session, we’ll review the TechFAR handbook objectives, key components and recommendations for getting agile adopted in your agency.

  • Liked Judy Neher
    keyboard_arrow_down

    Built in or Bolted On? Building Secure Systems with an Agile Team

    Judy Neher
    Judy Neher
    schedule 2 years ago
    Sold Out!
    60 mins
    Talk
    Intermediate

    With security being a historically waterfall process, how do we address the security of our system or application as an agile team?

     

    Through the lens of Scrum team members, we will examine the roles and responsibilities of individual team members to enable producing a secure product.

     

    Developers, testers and systems engineers all have specific obligations regarding the security of their product, but must bring those to bear in a collaborative fashion.  We will take each of these roles individually and focus on how their individual skillsets coalesce together to build a secure system.

  • Liked Michael Harris
    keyboard_arrow_down

    Introducing Agile to a PRINCE2 Environment in UK City Government

    Michael Harris
    Michael Harris
    schedule 2 years ago
    Sold Out!
    30 mins
    Case Study
    Beginner

    In early 2014, Mike Harris took on an agile training and coaching engagement for a small team with a big project - building a new website for the mayor and Assembly of major city in the UK.  This short case study will describe the oontext, the challenges, the successes and the failures of the engaagement. Mike will explain the easy and difficult aspects of working within a traditional project management framework, PRINCE2.

    Attendees should leave with an appreciation of how pragmatism and the goodwill of the participants can start to overcome the barriers to entry that apply in the government situation where rigid traditonal project management is in place and actual development is assumed to be outsourced.

  • Liked Roland Cuellar
    keyboard_arrow_down

    IV&V for Federal Agile Programs: A Customer Experience Report

    Roland Cuellar
    Roland Cuellar
    Ken
    Ken
    schedule 2 years ago
    Sold Out!
    60 mins
    Talk
    Intermediate
    1. Many federal government organizations have a requirement to perform independent verification and validation (IV&V) of software development projects for purposes of risk identification and compliance
    2. As more federal agencies move towards agile, they will need to devise agile-appropriate methods for evaulating agile teams and contractors for process performance and project risk identification
    3. Traditional approaches to IV&V are heavily biased towards waterfall, gate reviews, and traditional SDLC artifacts and hence, do not work well within an agile envrionment
    4. Agile programs have their own process-specific risks and issues that need to be evaluated uniquely.  The document-centric approach that has traditionally been used is innapropriate and ineffective for agile teams as it does not find the right risks and does not find them early enough in the development process.
    5. We at DHS/CIS have developed a unique, agile-appropriate IV&V model for a large agile transformation effort within DHS
    6. The model is used to discover process risks, design risks, code risks, and testing risks in real-time for agile teams
    7. The model serves as actionable and real-time feedback to teams, contractors, and federal managers that can be used for process improvement, vendor evaluation, and as a means to find and elevate delivery risks on agile projects
    8. Positive results, challenges, and recommendations related to the development, roll-out, and execution of this agile-appropriate IV&V model will  be shared
  • Liked Joshua Seckel
    keyboard_arrow_down

    No defects in a government setting? What does that really mean?

    Joshua Seckel
    Joshua Seckel
    schedule 2 years ago
    Sold Out!
    60 mins
    Talk
    Intermediate

    We have heard a lot about no defects or zero defects, but is that reasonable or achievable in the government context?  How else can each sprint be deployable? Or how can you get to true flow with each story deployed to production?

     This session will explore how to get to a no defects posture across all of the tests required in a government setting. 

    We will look at the various types of testing:

    Unit, Functional, Integration, Security, 508, System, User Acceptance, etc 

    We will look at what defects mean and how (or if) they should be tracked

    We will look at what potential impediments from government organziations may exist in reaching a no defect state of software delivery

    We will look at what tools and techniques can be used successfully in the government setting to address the impediments and achieve no defects in released software

Sorry, no proposals found under this section.