Feature Teams - getting started

[swhume]

Thanks for signing up for the Feature Teams. Our overall team size, along with the expanded scope of our project, made this possible. As you have noticed, we are not being overly prescriptive regarding how each team operates and communicates. We're also not dictating how the feature will be created or delivered. Our current high-level architecture imposes some constraints on your work, but in general, we'd like each Feature Team to define its work and how it will complete its deliverables. In a nutshell, we are using an agile-style methodology and expect teams to be self-organizing.

In many cases, a high-level issue exists in our backlog describing your team's feature. In cases where such an issue does not exist, we will create one. In all cases, we will attempt to add a bit more detail on the scope and aims for the work to help get you started. Despite being an agile-style project, we do not have a formal Product Owner creating the backlog. Each feature team will create the detailed issues in the backlog themselves. They should get input from the larger team and, where appropriate, other key stakeholders.

As each Feature Team's backlog is created, we can schedule some meeting time for that team to walk us through the key elements in the backlog. If the team has questions or gets blocked, we can help with those as well.

As was the case in 360i Phase 1, we expect exploratory work to be a part of the effort, planned or otherwise. In many cases, you will be working with new standards or technology unfamiliar to you, and perhaps something that has never been implemented before. This is one reason we prefer an agile-style methodology; we don't have a complete understanding of many aspects of the solution.

Many of the overarching objectives of our project were articulated in the slides we reviewed today. You can revisit those if you find them helpful. Objectives such as maximizing automation, starting from study design, using semantics (e.g., BCs, ACs), and identifying and resolving standards gaps apply to most Feature Teams.

It looks like our milestone dates may be moving a bit. Our next milestone is the Summer Release scheduled for July 31st. I've been told there will be a webinar to communicate our achievements. The US Interchange milestone has been moved up to September 1st. That doesn't leave us much time. Last I heard, they were planning to do demos at the US Interchange, so this will be a major milestone. Lastly, we hope to have an EOY DDE release, which will mark our final milestone of 2026.

This is a discussion, so add your thoughts and questions.

[rchaitanyapradeep]

Hi Sam. Can you please point out to the DTA to SDTM related information and files. Previously we have used different sources for SDTM automation, currently i understood that we need to use DTA/define.json as inputs. I have checked jira for any highlevel backlogs but i couldn't fiind them. Request your help on this.

[chowsanthony]

Created DTA feature team: Ideas for filling the backlog