|
|
|
|
|
| |
| |
| |
Developing and confirming requirements with user stories |
| |
Planning for small development iterations and internal releases |
| |
Sizing and justifying agile development projects |
| |
Employing automated unit and acceptance testing to drive project success |
| |
Using continuous integration to insure working software every day |
| |
Building cohesive development teams with agile project management |
| |
Determining when and when not to use agile development practices |
This course teaches you how to run a software development project from start to finish with proven agile development practices. Beginning with project selection and justification and working through planning and development, you will learn how to deliver software incrementally while meeting customers’ needs through close interaction. Learn how to select and justify projects that work best with agile development methods. Practice techniques of agile estimation and prioritization and find out how to track progress using velocity and burn-down charts.
Find out about agile requirements development techniques, represented first as user stories and later as automated acceptance tests. In hands-on exercises, you will write user stories and plan iterations and releases that deliver the most important functionality first. Learn to use continuous integration that insures working software throughout the development project and how test driven development enables this powerful process.
The roles and responsibilities of developers, managers, business analysts, and QA specialists are different with agile development. These differences are described in detail, with supporting case studies from experienced agile teams as reinforcement. Special attention is paid to the role of the QA specialists to bring them to the front of the process for a specification role.
The methods taught in this course synergize with the principles of Lean Software Development. By providing the most important features first, the agile team provides the customer a base on which to clearer about later requirements. They also can take advantage of what they've learned early during development. While this does require an attention to code quality to allow for an emerging architecture, there are established methods to do this.
This course is for development directors, project managers, team leaders, and programming leads who want to learn how to manage agile projects. It is also for QA directors, managers, and testers who want to understand their changing role in an agile organization. Business analysts and systems analysts and solution management should also attend to learn about their role in the agile structure.
|
|
|
| |
|
|
|
|
|
|
|