Agile (week 1) Flashcards
what does the agile manifesto say
we are uncovering better ways of doing it and helping others do it. through this work we have come to value :
- -> individuals and interactions over process and tools
- -> working software over comprehensive documentation
- -> customer collaboration over contract negotiation
- -> responding to change over following a plan
benefits of agile development
–> design of the product is efficient and fulfils the business requirements
–> there is a constant 2 way communication which keeps the customers involved, thus all the stakeholders have clear visibility on the project’s progress
–> the dev teams are quite responsive to the changes and can accommodate changes even in the advanced stages of development
–> the customers continuously get a look and feel of the project progress at the end of each iteration/sprint
–> each sprint provides the customer with working software which meets their expectation as per the definition of done provided by them
disadvantages of agile development
–> depends heavily on customer interaction, so if the customer is not clear, the project is driven in the wrong direction
–> total cost may be higher than waterfall
–> transfer of technology to new team members may be quite challenging due to lack of documentation
practices based upon the manifesto for agile software dev is called _____________
agile practices
what is a sprint in agile
it is a fixed length time boxed incremental approach to software development by advocating frequent interactions with businesses
what are agile events
Agile Events, (formerly Agile Ceremonies), are several types of meetings prescribed within Agile frameworks
what are the different agile events
- -> daily standup meeting
- -> sprint planning
- -> sprint review
- -> spring retrospective
how does kanban work
all the work items are represented as cards on a board allowing teams to visualise progress
what does kanban allow you to do
visualise what you do today
seeing all the items in context can be very informative
limit the amount in progress
helps balance the flow based approach so that teams dont start and commit to too much work at once
enhance flow
when something is finished the next highest thing is pulled from the backlog