The Developer Lead is responsible for the quality of the code delivered by the team’s core developers.

Code review and compliance with engagement Best Practices, Code Standards and established Design Patterns are enforced by the Developer Lead.

Any team member coaching, mentoring or training is the responsibility of the Developer Lead.

The Developer Lead can be a Sprint developer but the role’s primary responsibility is to ensure that the team is delivering quality and a sustainable code base for the QA Team to validate.

This role is a member of the Daily Scrum Stand Up Meetings but speaks only if development tasks are assigned.

The primary skill set for the UI Developer is Client-side Technologies. They role requires expert knowledge and experience with all aspects of the User Experience.

The Technology expertise required includes HTML, JavaScript, jQuery and related frameworks.

A strong knowledge of Cascading Style Sheets (CSS) and Client-side frameworks such as Angular, Knockout and Bootstrap are expected as well.

The role requires that any Client Technology that is selected for an engagement must be mastered.

This role is a speaking member of the Daily Scrum Stand Up Meetings and delivers to the Scrum Team the activities of the previous day, the planned activities of the current day and any blocks.

All resolution details are scheduled as an “Off-line” meeting, with the relevant Team Members. after the Stand up meeting by the Scrum Master.

This is generally a Model/View/Controller Web application but can be any Client-facing selected technology for the engagement.

The Application Developer must be experienced in all aspects of the designed solution. This includes support for the UI Developer and understanding of the SOA stack for support for the Back End Developer.

The Technology requirements include all Design Principles, Object Oriented Programming (OOP) Best Practices along with a good knowledge of the implementation of Design Patterns

All code developed by this role must be created using Test Driven Development (TDD).

The code must be first created within the Testing Framework standards defined for the Test Assemblies.

The code starts as a RED Failing test. This acts as a visual “To Do” list of defined Code validation abstractions. The test is then developed to pass in any way possible for the GREEN test. At this stage some Best Practices may be waived.

The most important task of the Application Developer is the YELLOW stage of TDD. The code within the Test Assembly, that passes now as a GREEN test, is moved into the Assembly under test and refactored into the Design Principles, Best Practices of OOP and comply with established Design Patterns.

Code Review of all developed code is essential for ensuring that the YELLOW refactoring is completed successfully. This action helps ensure that the code base delivered to the Client will lower the Total Cost of Ownership (TCO) throughout the Software Development Life Cycle (SDLC).

Knowledge of Aspect Oriented Programming (AOP) is required to implement the minimum Application-centric Cross Cutting Concerns provided by the Back End Developer for Error Handling, Logging, Instrumentation (Messaging) and Security.

This role is a speaking member of the Daily Scrum Stand Up Meetings and delivers to the Scrum Team the activities of the previous day, the planned activities of the current day and any blocks.

All resolution details are scheduled as an “Off-line” meeting, with the relevant Team Members. after the Stand up meeting by the Scrum Master.

The Back End Developer, sometimes referred to as a “Middleware Developer”, must be proficient in all aspects of the Service Oriented Architecture (SOA) stack. This includes Web Services that implement SOAP and REST architectures for cross-domain delivery of information for the Applications.

A strong knowledge of the Representational State Transfer (REST) architectural style and the concepts of State representation rather than concrete Methods implementation are required for this role.

A thorough knowledge of Data Layer Abstractions such as Object Relational Mapping (ORM) frameworks for Database Table representations as ORM framework objects is essential.

Intimate knowledge and experience with creating Repository Patterns using the Request/Response Design Pattern to transform collections of Entity Objects into single Complex Data Transfer Objects (DTOs) that can be serialized at the Web Services layer for Application consumption.

A strong skills with Business Rules and Rules Engines that are consumed on the Business Layer of the SOA stack is required to deliver efficient payloads to the Client Applications.

An understanding of Aspect Oriented Programming (AOP) is required to implement the Cross Cutting Concerns that all SOA assemblies with consume. They are AOP assemblies for Error Handling, Logging, Instrumentation (Messaging) and Security at a minimum.

An implementation of these Cross Cutting Concern assemblies will be used for Application-centric AOP requirements.

This role is a speaking member of the Daily Scrum Stand Up Meetings and delivers to the Scrum Team the activities of the previous day, the planned activities of the current day and any blocks.

All resolution details are scheduled as an “Off-line” meeting, with the relevant Team Members. after the Stand up meeting by the Scrum Master.

Requirements for new databases and modifications to the existing data repositories are defined by the Architects Team’s Data Architect and Database Analysts Statement of Works (SOW).

The requirements defined by the Data Architect’s SOWs are implemented by the Database Developer.

This role works with the Architect team to create functional requirements, modifies existing databases and data products according to the defined Client’s Data Domain needs.

Database Developers works with other Development Team members on topics related to Data Management and Data Manipulation and Reporting for the Daily Operations.

Database Developers are responsible for getting the “Data Right”.

Relational schema are the prime model for the Database Developer, using single rows and small subsets. Database Developer uses ETL (Extract, Transform and Load) skills mostly for Data Feeds

The Database Developer is responsible for the Transactional Database Model within the Client’s Data Domain. This is called Online Transactional Processing (OLTP).

The ability to create defined reports, as a Report Writer, is a skill set requirement for this role.

An understanding of Enterprise Data Management (EDM) to ensure database quality, and performance that serves both internal and external Client Users.

This role is a speaking member of the Daily Scrum Stand Up Meetings and delivers to the Scrum Team the activities of the previous day, the planned activities of the current day and any blocks.

All resolution details are scheduled as an “Off-line” meeting, with the relevant Team Members. after the Stand up meeting by the Scrum Master.

The BI Developer turns the Domain Data into “Actionable” Information.

Skills required is the ability to target a specific area for improvement, with quantifiable progress, given realistically achievable goals in a time frame that adds value to the Business Domain.

An intimate understanding of the Business Domain is required as Business Intelligence (BI) is being used more across all functions of the Domain’s Value Chain.

The Domain Knowledge Model that supports the Domain’s Value Chain is created by the BI Developer using Online Analytical Processing (OLAP) skills.

These skills include creating Fact Tables, Dimensions and Cube Structures primarily as Star schemas.

Data Mining, Data Warehouse and ETL (Extract, Transform and Load) skills are required to help create the Data Landscape to OLAP processing.

The BI Developer is responsible for loading Reporting Systems.

A solid understanding, implementation experience and tools for creating Enterprise Data Management (EDM) strategies to ensure database quality, and performance are required for a complete BI Developer.

This role is a speaking member of the Daily Scrum Stand Up Meetings and delivers to the Scrum Team the activities of the previous day, the planned activities of the current day and any blocks.

All resolution details are scheduled as an “Off-line” meeting, with the relevant Team Members. after the Stand up meeting by the Scrum Master.

The CI Manager also manages all “Code Pushes” to higher environments such as QA, Staging, a Production emulation environment, and Production.

All automated test suites and harnesses along with the required scripts are managed by the CI Manager.

The Web reports for the Business to monitor the Sprint development progress through Acceptance Test Driven Development (ATDD) Behavior Driven Design (BDD) tools such as SpecFlow are managed by the CI Manager as well.

The Continuous Integration Manager is responsible for success delivery of the Sprint Deployment code to QA and ultimately to Production.

This role is a speaking member of the Daily Scrum Stand Up Meetings and delivers to the Scrum Team the activities of the previous day, the planned activities of the current day and any blocks.

All resolution details are scheduled as an “Off-line” meeting, with the relevant Team Members. after the Stand up meeting by the Scrum Master.

The Code Review Manager assigns Code Review Leads to the approved Design Code Designs.

This role is responsibly for ensuring the scheduling of all Code Reviews and reviews Code Review follow-up requests, if required.

The Code Review Manager certifies that the code reviews has been completed successfully.

This role delegates the majority of the code review responsibilities to the assigned Code Review Lead.

This is a rotating role amongst all of the Development Team members.

The Code Review Manager delegate the scheduling responsibility to the assigned Code Review Leads.

This role selects a Code Technologist to act as an assistant for during the code review process.

The Code Review Lead will be responsible for secondary knowledge about the reviewed code base.

This role will be able to act as a “Alternate Proxy Developer” when required for Bug fixes and change management feature functionality requests when the original Developer and the Code Technologist is not available.

The Code Review Lead  role creates the third level depth of knowledge of the Client’s code base deliverables.

This is a rotating role amongst all of the Development Team members.

The Code Assistant will be responsible for primary knowledge about the reviewed code base.

This role will be able to act as a “Primary Proxy Developer” when required for Bug fixes and change management feature functionality requests when the original Developer is not available.

The Code Technologist role creates the second level depth of knowledge of the Client’s code base deliverables.

The Development Team is the Builder of the Technology Domain Entity solution.

The Domain Entity Data Model is create within the selected Development language such as C# and .NET and built on the defined Network Architecture.

The Cross Cutting Aspect of Security is designed to be available and applied as a Domain Component Level Authentication and Authorization concern.

The Software Development Forces of Nature are used as Design Constraints to help manage the forces at work such as Capacity and Latency (Affinity) along with Intermittent Failures.

The “Human Factor” is a design consideration, both intentional malicious attacks and unintentional human error.

The Data Entity models must be presented in “Process Flows” that create an “Enjoyable User Experience”.

A Functional Enterprise is extensible through Distributed Systems that can support heterogeneous Clients that can scale with time with minimum of design changes.

Changes in the Organizational Roles should not adversely affect the scalability and extensibility of the Functional Enterprise Business Technology Solution.

The deployed solution that creates the Functional Enterprise should be as non-temporal as possible.

Its Timing Cycles should be defined dynamically and driven by the Strategies of the Enterprise at a single point in space and time.