Please enable JavaScript.
Coggle requires JavaScript to display documents.
Agile Methodology for Data WareHouse and Data Integration Projects…
Agile Methodology for Data WareHouse and Data Integration Projects
Agile software development
Working Software over Comprehensive Documentation
Customer Collaboration over Contract Negotiation
Individuals and Interactions over processes and Tools
Responding to Change over Following a Plan
Agile Team Structure
Pig Roles
Pigs are committed to building software regularly and frequently, they are the ones producing the product.
Project team
The team has the responsibility to deliver the product. A team is typically made up of five to nine people with cross-functional skills who do the actual work (design, develop, test, etc.).
scrum master
Scrum is facilitated by a Scrum master, whose primary job is to remove impediments to the ability of the team to deliver the sprint goal. The Scrum Master is not the leader of the team (the team is self-organizing) but acts as a buffer between the team and any distracting influences. He or she acts as a facilitator.
Product owners
Product owners represent the customer. They review and prioritize the items for development. They are customer focused or customer-centric and are the key decision maker about whether the release is acceptable for production release.
Chicken Roles
Chicken roles are not part of the actual Scrum process and are not directly involved in construction of the product, but must be taken into account.
stakeholders (customers, vendors)
Stakeholders are the people who enable the project and for whom the project will produce the agreed-upon benefits. They are directly involved in development only during the sprint reviews.
Managers
The managers set up the environment for the product development organizations and provide resources for the agile team members
Principles of Agile Method
Projects are built around motivated individuals, who should be trusted
Continuous attention to technical excellence and good design
Face-to-face conversation is the best form of communication (co-location)
Simplicity
Close, daily cooperation between business people and developers
Self-organizing teams
Working software is the principal measure of progress
Regular adaptation to changing circumstances
Working software is delivered frequently (in weeks rather than months)
Customer satisfaction by rapid, continuous delivery of useful software
Even late changes in requirements are welcomed
Meetings in an agile lifecycle
sprint planning meeting
sprint review meeting
sprint retrospective meeting
release planning meeting
daily scrum