Agile Programming Professional (933)

Agile Software Development and Engineering Introduction

Defining programming best practices

• Identifying software development roles and activities
• Choosing plan-driven vs. Agile methodologies
• Waterfall
• V
• Spiral

Transitioning to Agile Development processes

• Comparing XP, Scrum, Lean, Kanban, Feature-Driven, Model-Driven and Test-Driven Developments
• Identifying Agile values, processes and best practices
• Determining ideal iteration length

Managing Agile Projects

Gathering software requirements

• Eliciting requirements from users
• Adopting Agile values
• Writing user stories

Planning Agile Projects

• Prioritizing and estimating work
• Estimating business value
• Organizing projects by features
• Dividing features into tasks

Reporting Team Progress

• Documenting work completed with backlogs
• Tracking progress with burn down charts
• Calculating velocity and adjusting to change
• Projecting project costs and completion dates
• Monitoring work in progress with task boards

Analyzing User and System Requirements

Modeling for Agile projects

• Depicting requirements with use case diagrams
• User-system interactions with activity diagrams
• Employing sequence and communication diagrams
• Describing system transitions with state diagrams

Detailing use cases

• Identifying actors and use cases
• Identifying pre- and post-conditions
• Specifying primary and alternative paths
• Documenting nonfunctional and system requirements

Architecting classes with UML

• Representing class data and behaviors
• Recognizing the need for inheritance
• Defining data requirements
• Specifying relationships and multiplicities

Test-Driven Development

Defining test levels

• Acceptance, system, integration and unit testing
• Employing both automated and manual testing
• Specifying boundary conditions
• Driving development through constant testing

Ensuring software meets requirements with user acceptance testing

• Scripting user acceptance tests
• Performing exploratory testing
• Specifying acceptance criteria
• Determining conditions of satisfaction

Minimizing bugs through automated programmer unit testing

• Utilizing tools for automated unit testing
• Writing unit test code
• Isolating classes for testing
• Programming mock objects
• Refactoring for improved design

Optimizing Productivity of Agile Teams

Building Agile teams

• Team member roles and responsibilities
• Managing teams for performance
• Scaling Agile for larger projects
• Cross-training and pairing for improved productivity
• Integrating ScrumMaster and Product Owner roles into the development team

Conducting Sprint reviews and retrospectives

• Techniques for gathering feedback
• Analyzing how to do better
• Adjusting to change
• Reflecting on Agile best practices

Analysts, programmers, designers, architects, testers and other development team members who want an introduction to modern software engineering skills and UML.