Dhurjati

Microservices - also known as the microservice architecture - is an architectural style that structures an application as a collection of services that are. Highly Maintainable and Testable. Loosely Coupled. Independently Deployable. Organized Around Business Capabilities.

The three things which are most important for the estimation are as follows: The complete User Story Past Experiences Any documentation that is being used by the organization Different estimation techniques Big/Uncertain/Small (BUS) T-Shirt Sizes - XS, S, M, L, XL Fibonacci Sequence

The definition of Ready is that the User Story is complete in all aspects like Who What Why and the Acceptance Criteria is well defined. The definition of Done is that it has passed all the Acceptance Criteria provided, code review has been done by the peer, clear and concise documentation has been provided for what has been accomplished and handed over to the Product Owner for review.

User Story is one of the features that need to be built for the product, described from the viewpoint of the end-user. The things to be captured in a User Story are as follows: Who - for whom is this being developed What - what is the goal that we want to achieve Why - what is the value that the end-user derives from this Each User Stroy needs to have proper Acceptance Criteria, which should be demo-able so that it can be reviewed by the Product Owner /  Stakeholders. The criteria specified should be testable and should clearly mention the pass / fail results Should be clear and concise SHould be defined with a shared understanding between the Product Owner and the Development Team. Rules for writing a good user story are as follows: I ndependent - one user story should not be dependent on another N egotiable - the user story should be able to adapt to changing scenario for the end-user V aluable - should give some concrete value to the end-user E stimateabl...

The building blocks of Scrum are as follows: Sprint - this is a time frame, e.g. 1 week to 4 weeks. Sprint Planning - this is to be facilitated by the Scrum Master and attended by the Development Team and most importantly the Product Owner. Daily Standup - this is to be facilitated by the Scrum Master and attended by the Development Team What did you do yesterday What are you going to do today  Any impediments that hinder in achieving the sprint goals Sprint Review - this is facilitated by the Scrum Master and attended by the Development Team, Product Owners and key stakeholders, held on the last day of the sprint. Sprint Retrospective - this is facilitated by the Scrum Master and attended by the Development Team. What went well What did not go well What needs to be improved upon Backlog Grooming (Refinement) - this happens when spring is already in progress. Getting the product backlogs refined, adding more to the user stories and getting it ready to pull out a...

Agile is a philosophy which is having the following values and principles: 4 Values Individuals and Interactions over Processes and Tools Working Software over Comprehensive Documentation Customer Collaboration over Contract Negotiation Responding to a change over Following a Plan 12 Principles Deliver Value Faster - Highest priority is to satisfy the customer through early and continuous delivery of valuable software Welcome Change - Welcome changing requirements, even late in the development process. The agile process harnesses change for the customer's competitive advantage. Deliver Working Software Frequently - Deliver working software frequently, from a couple of weeks to a couple of months, with a preference to the shorter timescale. Work Together Daily - Business people and developers should work daily throughout the project life span. Build Projects Around Motivated Individuals - Build projects around motivated individuals, give them the environment and...