[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"doc-seo-202915-105":3,"detail-sidebar-cat-0-en-105":85,"doc-detail-202915-en":135},{"code":4,"msg":5,"data":6},0,"ok",{"site_id":7,"language":8,"slug":9,"title":10,"keywords":11,"description":12,"schema_data":13,"social_meta":78,"head_meta":80,"extra_data":82,"updated_unix":84},105,"en","usace-cbest-agile-group-project-profile-agile-group-profile","USACE CBEST Agile Group Project Profile - Agile Group Profile","","US Army Corps of Engineers (USACE) contracted Agile Group to develop the Corps Business Execution Status Tracker (CBEST) using Microsoft SharePoint™. Customized coding was not allowed, so SharePoint out-of-the-box capabilities were leveraged to satisfy stakeholder needs. Multiple Systems of Records were combined into a single data cube, with security and single sign-on credentialing across authentication steps. Agile delivery used time-boxed sprints covering requirements, staged releases, beta testing, training over 150 end users, phased one-month deployment, and follow-on maintenance.",{"@graph":14,"@context":77},[15,34,56],{"@type":16,"itemListElement":17},"BreadcrumbList",[18,23,27,31],{"item":19,"name":20,"@type":21,"position":22},"https://docshare.wps.com","Home","ListItem",1,{"item":24,"name":25,"@type":21,"position":26},"https://docshare.wps.com/document/","Document",2,{"item":28,"name":29,"@type":21,"position":30},"https://docshare.wps.com/document/technology/","Technology",3,{"item":32,"name":10,"@type":21,"position":33},"https://docshare.wps.com/document/usace-cbest-agile-group-project-profile-agile-group-profile/202915/",4,{"url":32,"name":10,"@type":35,"image":36,"author":41,"headline":10,"publisher":44,"fileFormat":47,"inLanguage":8,"description":12,"dateModified":48,"datePublished":49,"encodingFormat":47,"isAccessibleForFree":50,"interactionStatistic":51},"DigitalDocument",{"url":37,"@type":38,"width":39,"height":40},"https://docshare.wps.com/thumbnails/usace-cbest-agile-group-project-profile-agile-group-profile/202915.png","ImageObject",300,407,{"name":42,"@type":43},"Stanley","Person",{"url":19,"name":45,"@type":46},"DocShare","Organization","application/pdf","2026-10-14","2026-09-04",true,{"@type":52,"interactionType":53,"userInteractionCount":55},"InteractionCounter",{"@type":54},"ViewAction",12,{"@type":57,"mainEntity":58},"FAQPage",[59,65,69,73],{"name":60,"@type":61,"acceptedAnswer":62},"What is CBEST and who requested it?","Question",{"text":63,"@type":64},"CBEST is the Corps Business Execution Status Tracker. It was developed for the US Army Corps of Engineers (USACE) Omaha District under a contracted effort by Agile Group.","Answer",{"name":66,"@type":61,"acceptedAnswer":67},"Why was Microsoft SharePoint used, and what constraint affected development?",{"text":68,"@type":64},"CBEST was built using Microsoft SharePoint™. USACE IT did not permit customized coding, so Agile relied heavily on SharePoint’s out-of-the-box solutions.",{"name":70,"@type":61,"acceptedAnswer":71},"How were stakeholder requirements handled and released?",{"text":72,"@type":64},"Requirements were organized into business, stakeholder, functional, non-functional, and UI requirements. Delivery followed a four-stage release schedule: concept, pilot, working, and final releases.",{"name":74,"@type":61,"acceptedAnswer":75},"What testing, training, and deployment activities were completed?",{"text":76,"@type":64},"Agile designed beta testing tracking sheets for a broad set of functional testers, built a comprehensive POI to train 150+ end users and 50 stakeholders, and completed a phased one-month rollout to support a large USACE district, using satisfaction surveys and follow-on maintenance.","https://schema.org",{"og:url":32,"og:type":79,"og:title":10,"og:site_name":45,"og:description":12},"article",{"robots":81,"canonical":32},"index,follow",{"doc_id":83,"site_id":7},202915,1788552283,{"code":4,"msg":86,"data":87},"success",[88,92,96,100,105,109,114,119,124,127,131],{"id":22,"doc_module":4,"doc_module_name":25,"category_name":89,"show_sort_weight":90,"slug":91},"Story & Novel",90,"story-novel",{"id":26,"doc_module":4,"doc_module_name":25,"category_name":93,"show_sort_weight":94,"slug":95},"Literature",80,"literature",{"id":33,"doc_module":4,"doc_module_name":25,"category_name":97,"show_sort_weight":98,"slug":99},"Exam",70,"exam",{"id":101,"doc_module":4,"doc_module_name":25,"category_name":102,"show_sort_weight":103,"slug":104},5,"Comic",60,"comic",{"id":106,"doc_module":4,"doc_module_name":25,"category_name":29,"show_sort_weight":107,"slug":108},6,50,"technology",{"id":110,"doc_module":4,"doc_module_name":25,"category_name":111,"show_sort_weight":112,"slug":113},7,"Healthcare",40,"healthcare",{"id":115,"doc_module":4,"doc_module_name":25,"category_name":116,"show_sort_weight":117,"slug":118},8,"Research & Report",30,"research-report",{"id":120,"doc_module":4,"doc_module_name":25,"category_name":121,"show_sort_weight":122,"slug":123},9,"Religion & Spirituality",20,"religion-spirituality",{"id":122,"doc_module":4,"doc_module_name":25,"category_name":125,"show_sort_weight":122,"slug":126},"World Cup","world-cup",{"id":128,"doc_module":4,"doc_module_name":25,"category_name":129,"show_sort_weight":128,"slug":130},10,"Lifestyle","lifestyle",{"id":132,"doc_module":4,"doc_module_name":25,"category_name":133,"show_sort_weight":101,"slug":134},19,"General","general",{"code":4,"msg":86,"data":136},{"doc_id":83,"user_id":137,"nickname":42,"user_avatar":138,"doc_module":4,"category_id":106,"category_name":29,"doc_title":10,"doc_description":12,"doc_content":139,"file_id":140,"file_url":141,"file_type":142,"file_size":143,"view_count":55,"is_deleted":4,"is_public":22,"is_downloadable":22,"audit_status":22,"page_count":22,"language":144,"language_code":8,"site_id":7,"html_lang":8,"table_of_contents":145,"faqs":146,"seo_title":147,"seo_description":12,"update_tm":84,"read_time":30},2336477405376,"https://ap-avatar.wpscdn.com/davatar_29158cc5080c5b710cf443261637dec0","CLIENT: US Army Corps of Engineers (USACE)  \nQUALIFICATION: Corps Business Execution Status Tracker (CBEST)  \nAgile Group  \nA certified 8(a), Woman Owned Small Business (WOSB), Agile Group is a niche firm supporting government and commercial clients throughout the world to better manage, measure, and communicate their project portfolios. Agile brings a decade of Federal Government experience with software development, PMO development, project management and controls, process improvement, and training. We deliver these solutions and related services for Federal agencies including the U.S. Army Corps of Engineers (USACE), and U.S. Customs and Border Protection (CBP).  \nCorps Business Execution Status Tracker (CBEST)  \nAgile Group was contracted by the USACE Omaha District to develop CBEST using Microsoft SharePoint™. Customized coding was inadmissible by USACE IT – therefore the out of the box solutions available with SharePoint were highly leveraged to meet all stakeholder requirements. Numerous Systems of Records (SoRs) were mashed to create single data cube to feed the CBEST tool, and security and single-sign-on credentialing were applied to each step of the authentication process. Through carefully timed Agile-methodology sprints, efficiency, effectiveness, and reliability were embedded in System Engineering Lifecycle (SELC) .  \nBest Value  \n Retaining a deep experience working with U.S. Federal Government, including Customs and Border Protection and USACE  \n Executing two multimillion-dollar CBP contracts for an array of services across disparate and geographically dispersed offices  \n Building highly complex software tools to meet the diverse needs of a wide-breadth of functionallydiverse Federal business units  \nBusiness Requirements ~~  ~~Business Requirements. Identified high-level USACE business goals. | Stakeholders Requirements. Outlined program & project needs. Functional Requirements. Addressed CBEST functionality in detail. | Non-Functional Requirements. Established goals of reliability, scalability, security, integration, etc. | UI Requirements. Noted as the most integral part of CBEST requirements.  \nDesign and Development ~~ ~~  \nStory boarded CBEST for stakeholder approval. Designed and methodically produced a four (4) stage release schedule of concept, pilot, working, and final releases. Staged in coordination with USACE Information Technology team and timeline.  \nTesting ~~ ~~  \nDesigned beta testing tracking sheets for a wide-breadth of functional testers to include Agile subject matter experts, USACE SMEs, USACE project, stakeholders, and end-users. Captured bugs, identified opportunities for improvement, and implemented solutions.  \nTraining ~~ ~~  \nDeveloped a comprehensive Program of Instruction (POI) to identify the materials necessary and approach required, to train over 150 endusers, and 50 project stakeholders. Employed multiple classroom events, and webinar delivery methods.  \nDeployment ~~ ~~  \nSuccessfully rolled out a fully-vetted, bug-free Corps Business Execution Status Tracker (CBEST) tool to end-users in support of a 900 person $1 . 5B dollar USACE District. Spanned a controlled and phased deployment period of one-month. Noted user experiences through in-depth satisfaction surveys and made updates to CBEST tool through a follow-on maintenance phase. NOTE: CBEST was piloted at the USACE Omaha District and is slated for USACE Enterprise-wide deployment.","cbCaisQVjjlmYJDB","https://ap.wps.com/l/cbCaisQVjjlmYJDB","pdf",1767434,"English","# CBEST Overview\n## Agile Group Background\n## Project Approach and Constraints\n# Business Requirements\n# Design and Development\n# Testing\n# Training\n# Deployment","[{\"question\":\"What is CBEST and who requested it?\",\"answer\":\"CBEST is the Corps Business Execution Status Tracker. It was developed for the US Army Corps of Engineers (USACE) Omaha District under a contracted effort by Agile Group.\"},{\"question\":\"Why was Microsoft SharePoint used, and what constraint affected development?\",\"answer\":\"CBEST was built using Microsoft SharePoint™. USACE IT did not permit customized coding, so Agile relied heavily on SharePoint’s out-of-the-box solutions.\"},{\"question\":\"How were stakeholder requirements handled and released?\",\"answer\":\"Requirements were organized into business, stakeholder, functional, non-functional, and UI requirements. Delivery followed a four-stage release schedule: concept, pilot, working, and final releases.\"},{\"question\":\"What testing, training, and deployment activities were completed?\",\"answer\":\"Agile designed beta testing tracking sheets for a broad set of functional testers, built a comprehensive POI to train 150+ end users and 50 stakeholders, and completed a phased one-month rollout to support a large USACE district, using satisfaction surveys and follow-on maintenance.\"}]","USACE CBEST Agile Group Project Profile - Agile Group Profile | PDF"]