tag:blogger.com,1999:blog-89891439123743242Sat, 05 Oct 2024 02:05:29 +0000agilexpscrumExtreme ProgrammingCodingagile xpsoftwareCodeCode NormalizationCode SmellDo The Simplest Thing That Could Possibly WorkFluentIterationLazy ProgrammerNot Invented HereOnce and Only OnceOne Responsibility RuleResponsibility Driven DesignScrum definitionSpecial formattingStandardXP agileYagniYou Arent Gonna Need Itagile planningagile story task estimatechickencontinuous buildscontinuous integrationcore practicesdevelopmentdownloadfreematrixmeasurementopen sourcepigplanning pokerproduct backlogproduct sheetproject managementqualitysoftwaresswtime estimationunit testunit testingvelocityxp xtudesxtreme programmingThis blog is for those geeks who are interested in AGILE based development model. AGILE is a breakthrough, a cutting edge framework which has been followed by many Fortune 500 companies. I would like to take AGILE one step ahead. So, lets call it AGILE++http://agileplusplus.blogspot.com/noreply@blogger.com (Rahul Choudhary)Blogger15125tag:blogger.com,1999:blog-89891439123743242.post-4946139610859772795Wed, 01 Jul 2009 04:52:00 +00002009-07-01T10:24:28.190+05:30agileCodingExtreme Programmingunit testunit testingxpThis practise is also known by many other jargons like Test Driven Development, Test Driven Programming, Test First Design etc.What is the underlying objective is to let you know that you need to avoid writing a single line of code till you have not written to test it. It is nothing but saying in a broader term that if the requirements are not clear the project will go down the drain. Now take http://agileplusplus.blogspot.com/2009/07/code-unit-test-first.htmlnoreply@blogger.com (Rahul Choudhary)0tag:blogger.com,1999:blog-89891439123743242.post-8572730890425787409Sat, 20 Jun 2009 21:35:00 +00002009-06-21T03:13:38.545+05:30agilecontinuous buildscontinuous integrationdownloadfreeopen sourcesoftwaresoftwaresswxpContinuous Build is a very vital aspect of Agile Methodology. It helps you recover quickly and allows bugs to be discovered early. It also put focus on Continuous Integration which is a entirely different subject altogether.The concept of Continuous build implies that the code should be checked out from the repository often and the test should be carried out frequently to ensure that the builds http://agileplusplus.blogspot.com/2009/06/continuous-builds.htmlnoreply@blogger.com (Rahul Choudhary)0tag:blogger.com,1999:blog-89891439123743242.post-436931108210563653Thu, 26 Mar 2009 20:43:00 +00002009-06-17T21:54:28.633+05:30agiledevelopmentIterationmatrixmeasurementproject managementqualitysoftwarevelocityToday I will talk about one of the most difficult topic faced by any Project Manager, you got it I am talking about Quality Assurance. Matrix and Number is agile are quite tricky and have to be dealt separately than a normal Project Matrix. I faced it when my company was preparing for CMMi L5 audit and the auditor didn't knew how to deal with a Agile project. He kept asking stupid questions and Ihttp://agileplusplus.blogspot.com/2009/03/agile-for-quality-assurance.htmlnoreply@blogger.com (Rahul Choudhary)0tag:blogger.com,1999:blog-89891439123743242.post-3866780079752467261Thu, 25 Sep 2008 05:03:00 +00002008-09-25T10:34:43.317+05:30agile story task estimateINVEST in Good Stories, and SMART TasksXP teams have to manage stories and tasks. The INVEST and SMART acronyms can remind teams of the good characteristics of each.In XP, we think of requirements of coming in the form of user stories. It would be easy to mistake the story card for the "whole story," but Ron Jeffries points out that stories in XP have three components: Cards (their physical http://agileplusplus.blogspot.com/2008/09/invest-in-good-stories-and-smart-tasks.htmlnoreply@blogger.com (Rahul Choudhary)0tag:blogger.com,1999:blog-89891439123743242.post-7130628331325611476Thu, 04 Sep 2008 04:38:00 +00002008-09-04T10:12:44.984+05:30Pairing Pattern: Ping Pong Pairing One of the struggles people can have when they first start pairing, is understanding when it is time to drive, and when it is time to watch. Developing a good tempo to the act of pairing – and understanding when the change over should occur – can make it seem like a much more fluid activity. When it is working well, outsiders will see the keyboard moving http://agileplusplus.blogspot.com/2008/09/pairing-pattern-ping-pong-pairing.htmlnoreply@blogger.com (Rahul Choudhary)0tag:blogger.com,1999:blog-89891439123743242.post-1729561515910858786Fri, 20 Jun 2008 07:00:00 +00002008-06-20T14:04:05.314+05:30CodeCodingFluentStandardxpxtreme programmingI just read a good article by Martin Flower on "Fluent Interface". Here is the abstract...A few months ago I attended a workshop with Eric Evans, and he talked about a certain style of interface which we decided to name a fluent interface. It's not a common style, but one we think should be better known. Probably the best way to describe it is by example.The simplest example is probably from http://agileplusplus.blogspot.com/2008/06/fluent-interface.htmlnoreply@blogger.com (Rahul Choudhary)0tag:blogger.com,1999:blog-89891439123743242.post-3603940269021220943Wed, 04 Jun 2008 09:59:00 +00002008-06-04T16:17:54.182+05:30agilescrumI was attending SCRUM meeting with my team and normally it is followed by a 5 min TIDBIT session by anyone on a round robin basis. One of my team member raised a very good point, he was giving example of how we have successfully implemented Agile in our team. And he pointed out that we have brought in incremental changes. That means we have implemented Agile in the Agile way. We didn't rushed http://agileplusplus.blogspot.com/2008/06/implementing-agile-in-agile-manner.htmlnoreply@blogger.com (Rahul Choudhary)0tag:blogger.com,1999:blog-89891439123743242.post-6535695534439807630Sat, 24 May 2008 14:59:00 +00002008-05-24T21:11:56.300+05:30agilescrumScrum definitionWhat is Scrum?A variation on Sashimi, an "all-at-once" approach to software engineering. Both Scrum and Sashimi are suited best to new product development rather than extended development. Sashimi originated with the Japanese and their experiences with the Waterfall model. They had the same problems with the Waterfall model as everybody else, so they adapted it to suit their own style. Realizing http://agileplusplus.blogspot.com/2008/05/scrum-unplugged.htmlnoreply@blogger.com (Rahul Choudhary)0tag:blogger.com,1999:blog-89891439123743242.post-6950694926536225467Wed, 21 May 2008 07:14:00 +00002008-12-11T02:04:45.223+05:30agileagile planningplanning pokertime estimationTime estimating using planning pokerEstimating is a team activity - every team member is usually involved in estimating every story. Why?As per Agile at the time of planning, we normally don’t know exactly who will be implementing which parts of which stories. Stories normally involve several people and different types of expertise (user interface design, coding, testing, etc).In order to providehttp://agileplusplus.blogspot.com/2008/05/planning-poker-time-estimations.htmlnoreply@blogger.com (Rahul Choudhary)1tag:blogger.com,1999:blog-89891439123743242.post-2174141853937248212Mon, 19 May 2008 10:40:00 +00002008-05-19T16:28:11.352+05:30agileagile xpcore practicesExtreme Programmingscrumxpxp xtudesThe 12 “XP Xtudes” (Xtude is XP means ‘Attitude’) of Extreme Programming (XP) grouped into four categories 1. Fine Scale feedbackXP thrives on providing feedback at smaller intervals with higher frequency. This allows controlling deviation at the right time, since in software or any othe industry for that matter, once deviation starts happening it is dificult to control at the later stages.Test http://agileplusplus.blogspot.com/2008/05/extreme-programming-core-practices.htmlnoreply@blogger.com (Rahul Choudhary)0tag:blogger.com,1999:blog-89891439123743242.post-7749719241148165571Tue, 13 May 2008 09:08:00 +00002008-05-13T15:23:52.531+05:30agileExtreme ProgrammingxpYagniYou Arent Gonna Need ItYAGNI perfectly sums up XP (Xtreme Programming). Here is why and how."You Arent Gonna Need It" (often abbreviated YAGNI) is an Extreme Programming (XP)practice which states:"Always implement things when you actually need them, never when you just foresee that you need them." Even if you're totally, totally, totally sure that you'll need a feature later on, don't implement it now. Usually, it'll http://agileplusplus.blogspot.com/2008/05/yagni.htmlnoreply@blogger.com (Rahul Choudhary)0tag:blogger.com,1999:blog-89891439123743242.post-8878322342295512419Tue, 13 May 2008 07:00:00 +00002008-05-13T14:49:20.478+05:30Code NormalizationCode SmellDo The Simplest Thing That Could Possibly WorkOnce and Only OnceOne Responsibility RuleResponsibility Driven DesignSpecial formattingFrom Bertrand Meyer's “Object Oriented Software Construction”, there was the statement:A class has a single responsibility: it does it all, does it well, and does it only.Classes, interfaces, functions, etc. all become large and bloated when they're trying to do too many things.When a function has too many responsibilities, it becomes buried deep in "Special Formatting", which has a "Code Smell".http://agileplusplus.blogspot.com/2008/05/one-responsibility-rule.htmlnoreply@blogger.com (Rahul Choudhary)0tag:blogger.com,1999:blog-89891439123743242.post-2363993764184154380Fri, 09 May 2008 06:39:00 +00002008-12-11T02:04:45.522+05:30Lazy ProgrammerNot Invented HereXP agile