Posts
Introduction Earlier we saw more software failures simply because of planning or estimating. When Agile is used, failures have been reduced significantly since it gives iterative releases based on the changing customer's needs with an approach of frequent planning and estimating. So here we see the article called "How to start planning and estimating projects in AGILE". This is an overview of what measure the project estimate can be done and how to we measure it. In what way we can measure the velocity of a TEAM. With the foundation I am creating in this article, I shall tell you the various techniques for estimating and re-estimating strategies in my next article. The Size of ESTIMATION Agile Teams separates estimates of size from estimates of duration. The size of the work should be estimated first before deriving the duration of it. Let us discuss this with a day to day life example. In your house suppose you are assigned the task to move the location of a sofa set
In my previous article , we have discussed what is Agile Story Point Estimation. In this article, we will learn how to estimate story points using "Planning Poker" cards. Planning Poker is a relative estimation technique used by teams to estimate the user story. Before starting, the planning poker team will define and agree on the parameters to measure the amount of work like a number of screens and number of fields etc. Identify a reference story that the team has done before or understands very well. Ideally, they will compare other stories with the reference story and one by one do the estimation. Steps Product Owner will explain the story to be estimated and the development team will ask questions if they have any issues or unclarity. For example - Design Related- Do we have to learn new things before starting the design/HTML/jQuery etc? Coding Related- Do we have any code class library ready or we have to write it from the scratch? Testing Related- Any specif
In my previous articles, we have discussed Agile Story Point Estimation and Agile Story Point Estimation Techniques - Planning Poker . In this article, we will learn Story Point Estimation using T-Shirt Size Technique. What is T-shirt sizing? T-shirt Sizing is one of the Story points sizing technique to estimate user story usually used in agile projects. It's a relative Estimation Technique. Rather than using a number of planning pokers, here, Items are classified into t-shirt sizes: XS, S, M, L, XL. The term originates from the way T-shirt sizes are indicated in the US. Rather than having T-shirts in sizes 4, 5, 6 etc, there are just a few sizes: Small (S), Medium (M), Large (L) and Extra Large (XL) and so on. With T-shirt measuring, the development team is made a request to evaluate whether they think a story is extra-small, small, medium, large, extra-large, or double extra-large. By expelling the numerical score, the development team is allowed to think in a mor
In my previous article , we have discussed User Story in Agile Scrum. In this article, we will learn what Story Point is and what Story Point Estimation techniques are. Story Point in Agile Scrum A Story Point is a unit of measurement of the overall effort needed to complete specific requirements of a product backlog item. When we have our product backlog ready and when a team is ready for next sprint, they pull the priority user stories from the product backlog and start estimation for completing the user stories. Story Point Estimation In any project, estimation plays a major role. It's very important in terms of the project budget, scope, and also to track the progress of the project against each milestone. image source : https://www.youtube.com/watch?v=sCCUEtjCpCs Estimation is a Team Sport and involves all team members like all developers, designers, testers, deployers on the team is key. The main benefits of involving the team to estimate is we are giving
In this article, we will learn what User Story is and how to write one. User Story plays a major role here. It is the part of the Agile process where instead of writing comprehensive requirements, we write a short description of a feature. As the Agile Manifesto says 'Working Software' Over 'Comprehensive Documents'. What is User Story? User Story is a short and simple description of the feature or requirements of the project. Generally, user stories are written on sticky notes or index cards as a user or role-based perspective. User Story Template As a < type of user or role >, I want < some goal > so that < some reason >. The template identifies 3 questions - "Who", "What", and "Why". If the team doesn't know these three answers, it means they don't understand the story, and if they don't understand the story, then it's difficult to split it well. Reference:https://mazoea.wordpres
Mapping the CMMI and Scrum CMMI practices are designed to provide value across a range of different situations and thus are stated in general terms. Because CMMI does not endorse any particular approach to development, little approach-specific information is provided. Therefore, those who don’t have prior experience implementing CMMI in situations similar to their current situation may find it difficult to interpret the practices. The following tables identify relevant CMMI practices for complying with maturity level 2 (using text taken from the model). They also show how Scrum practices were implemented in each CMMI specific practice (SP) on the large project. To be appraised at maturity level 2, the Scrum implementation had to show evidence of CMMI practices being performed. A discussion of the program’s CMMI maturity level 3 processes follows later. CMMI Maturity Level 2 Process Areas Requirements Management The purpose of requirements management (REQM) is to manage the pr
A User Story is a short description of something that your customer will do when they come to your website or use your application/software, focused on the value or result they get from doing this thing. User stories are: written from the point of view of a person using your website or application written in the language that your customers would use. Three C’s of the user story: Card – stories are traditionally written on note cards, and these cards can be annotated with extra details Conversation – details behind the story come out through conversations with the Product Owner Confirmation – acceptance tests confirm the story is finished and working as intended. Template for User Stories : A user story template often uses the following type of format: As a <role> , I want <feature> so that <reason> . Examples of user stories are: As a user , I want to upload photos so that I can share photos with others . Above are the examples of User Stories. We will ke