information contained in this slides are my own view gained through various experiences. •The images used in this slides were derived from various other online resources. •This is a technical session that contain non- technical content. •Get relaxed to get ready for some detailed presentation.
Individuals and Interactions over Processes and Tools • Working Software over Comprehensive Documentation • Customer Collaboration over Contract Negotiation • Responding To Change over Following a Plan
Continuous Delivery • The highest priority is to satisfy the customer through early and continuous delivery of valuable software. • Working software is the primary measure of progress.
Requirements • Welcome changing requirements, even late in development. • Agile processes harness change for the customer's competitive advantage. • This is nice customer expectation management also one of the marketing / sales pitfalls of agile software development. Coding Aspect : The development and architecture should be always Open for Extension, but closed for modifications.
and Developers Work Together The Product owner and Developers must work together daily throughout the project which helps to • Define the features of the product • Decide a release date • Prioritize feature according to change • Adjust features and priority for iterations • Accept or Reject work result for the sprint Daily Standup
• The code should always be Open for Extension, but Closed for Modification • Creating unit test along with Integration testing with each sprint • Modular and Expandable • Following SOLID principles may prove beneficial • Self dependency
tattaka
kou_kita
pichuang
tadashi_sato
masakiokuda
soudai
lufthanahelpsupport
hr01
airtravelguide
shinya337
bluehatbrit
lycorptech_jp
vanstee
jonrohan
reverentgeek
tanoku
productmarketing
aki_iinuma
kevinliebholz
caitiem20
maltzj
smashingmag
lemiorhan
keathley
