My Life

Archive for the ‘Agile Software Development’ Category

Agile Software Development

What is Scrum?
Scrum is an agile approach for developing innovative products and services, scrum is based a small set of core values, principles, and practices.
Why Scrum?
– Scrum can be use on software project that operated in a complex domain where more was unknown than known.
– Scrum can be use to avoid big up-front architecture design
– Scrum are more balanced approach to design, which included some design up front combined with a healthy dose of emergent, just- in-time design
– Scrum make teams to be more cross-functional
Scrum Benefit?
– Delighted customer
– Improve return to investment
– Reduce Cost
– Fast Result
– Confidence to succeed in a complex world
– More Joy

Scrum Roles
Scrum development efforts consist of one or more Scrum teams, each made up of three Scrum roles: product owner, ScrumMaster, and the development team.
Product Owner
The product owner is the empowered central point of product leadership. Product owner is the single authority responsible for deciding which features and functionality to build and the order in which to build them. Product owner maintains and communicates to all other participants a clear vision of what the Scrum team is trying to achieve. Product owner is responsible for the overall success of the solution being developed or maintained.
Scrum Master
Scrum Master helps everyone involved understand and embrace the Scrum values, principles, and practices. Scrum Master acts as a coach, providing process leadership and helping the
Scrum team and the rest of the organization develop their own high-performance, organization-specific Scrum approach.
Product Grooming: activity of creating and refining product backlog items, estimating them, and prioritizing them
Sprint: work is performed in iterations or cycles of up to a calendar month
The collection of these tasks, along with their associated product backlog items, forms a second backlog called the sprint backlog
Agile Principles
 Variability & Uncertainly
 Prediction and Adaptation
 Validated Learning
 Work in Process
 Progress
 Perfomance
User Stories Card is a common template format for writing user s to specify a class of users (the user role), what that class of users wants to achieve (the goal), and why the users want to achieve the goal (the benefit). A user story also contains confirmation information in the form of conditions of satisfaction.
Good Characteristic Product Backlog
 Detailed Appropriately
 Emergent
 Estimated
 Prioritized
PBI(Product Backlog Items) Estimation Concepts
 Estimate as a team
 Estimates are not commitment
 Focus on accuracy, not precision
 Use relative versus absolute sizes
The estimates ought to be a realistic measure of how big something is. We don’t want them artificially inflated due to external influences.
Velocity is the amount of work completed each sprint. It is measured by adding the sizes of the PBIs that are completed by the end of the sprint. Velocity measures output (the size of what was delivered), not outcome (the value of what was delivered).

• SHORT DURATION BENEFITS

• SCRUM FRAMEWORKS

• SOFTWARE DEVELOPMENT DISORDER
•