background preloader

Control Chaos - Control Chaos

Control Chaos - Control Chaos
Related:  Project Management Theory

What is Extreme Programming (XP)? - Definition from Extreme Programming (XP) is a pragmatic approach to program development that emphasizes business results first and takes an incremental, get-something-started approach to building the product, using continual testing and revision. Kent Beck, author of Extreme Programming Explained: Embrace Change, developed the XP concept. According to Beck, code comes first in XP. However, Beck emphasizes that in order to write the code, you have to write a test for it first so that you will know when your code succeeds. Beck calls Extreme Programming a "lightweight methodology" that challenges the assumption that getting the software right the first time is the most economical approach in the long run. This was last updated in August 2008 Email Alerts Register now to receive news, tips and more, delivered to your inbox. By submitting you agree to receive email from TechTarget and its partners. More News and Tutorials

Agile Alliance: Agile Alliance Home Jim Shore on what seperates high performing agile teams from jus I found a talk by Jim Shore at the Dallas chapter of the APLNtalk on what separates the great teams from the average agile teams (it is over an hour long): Since I had no good ideas this morning I just took notes. 1. High Bandwidth Communication High performing teams sit together. Teasley study shows that sitting together doubles productivity and time to market is one third: you separate a team because of convenience is it worth the cost. 2. Cult of quality: the believe they are special and are accomplishing something special. Talks about teams forming: Someone asks if you lose one member does it take another year to incorporate a new team member. There is a focus on continuous improvement (much like Lean's perfection principle). 3. Running tested features on a schedule every iteration. 4.

eero - Finally, WiFi that works Software Process Models Many process models I came across so far have their background in a certain engineering setup which I call "the happy engineering world". I called it this way, because in this "world" you design systems where requirements can be set up from the beginning, sub-components may be even available to a large extend and very often resources are not strictly limited. As an example may serve an airport traffic control system. However, there is also a quite different world and this is mostly forgotten by the preachers of process models. The spiral model would have been a solution too, however there are these nasty risk analysis phases which we did not want to do and which made not much sense in our situation. The Waterfall Model The waterfall model is believed to have been the first process model which was introduced and widely followed in software engineering. As programs became bigger the need for a better requirements phase, some more thoughts on the design, etc. were needed. The V Model

Agile Software Development The Big List of Agile Practices This post is probably going to be hated and loved at the same time. Because, when people talk about agile practices, they can sometimes become very religious. Which means I may be putting my head in a noose with this one. But who cares. You see, at different occasions I had wanted the availability of a big list of agile practices. Disclaimer: the list below is definitely incomplete, and probably controversial! I constructed the list below from practices found on eight different web sites. If you disagree with the list, or if you think some practices are missing, please let me know! You see, I am considering to use this list for a poll on agile practices and how they are being applied. Thanks already! ReferencesWiki = WikipediaSA = Scrum AllianceMG = Mountain Goat SoftwareC2 = Cunningham & CunninghamAM = Agile ModelingJS = James ShoreXP = Extreme ProgrammingIXP = Industrial XP (picture by the toe stubber)

Agile Test Methodology Vs V Model The object of the article is to uncover the disadvantages of the traditional V model of testing over the Agile test methodology. In doing so we will cover the following points: What is V model? Advantages and disadvantages of V model.What is Agile Testing? V model V-model is a software development model that is based on the relationships between each phase of the development life cycle as described in a typical Waterfall model of software development and its associated phase of testing Agile Test Methodology Vs V Model Figure 1 The V-model involves building a logical V shape sequence where the testing techniques associated with the design are reflected as descending and are applied for the “verification” and connected to the requirements or specifications parts are reflected as ascending and are applied for “validation”. The V-Model is a Software life cycle model. It explains how you go from high level concept to released product. Advantages of V Model Disadvantages of V Model Agile Testing

Agile Software Development: How To Implement Scrum In 10 Easy St So you’ve got your backlog in order , estimated your backlog , clarified your requirements , planned your sprint and created a collaborative workspace . You’ve sprinted to achieve your sprint goals , run daily stand-up meetings and tracked progress with a daily burndown chart . Now you’ve come to the end of your Sprint and finished when you said you would . All that’s left to do now, is Review, Reflect and Repeat… At the end of the Sprint, hold a Sprint Review meeting. Review what was delivered in the Sprint. The purpose of the Sprint Review is three-fold: It allows team members to show what they’ve achieved and demonstrate their contribution to the product. It allows all key stakeholders to see what’s been done, and provide valuable feedback on a regular basis, while there’s still time to take it on board. It helps the team to stay focused on the deadline of the Sprint - no-one wants to show up at the Sprint Review with nothing useful to demo. Together the team should: . What went well. Kelly.

26 Hints for Agile Software Development October 21, 2009 | Author: PM Hut | Filed under: Agile Project Management 26 Hints for Agile Software Development By Keith Swenson I collect nuggets of wisdom on various topics. Recently I have been going over the topic of Agile software development; what really matters? Below is a list of 26 key principles to guide an agile software development team. Get case 1 fully working before starting case 2. These are presented in no particular order. Original article can be found here. Keith Swenson is Vice President of Research and Development at Fujitsu America Inc. and is the Chief Software Architect for the Interstage family of products. Related Articles

The Death of the V-Model The V-Model of software development is widely in use today, especially in the defence industry. It’s a pity then, that it is fundamentally flawed, and that it is responsible for misleading project managers into thinking that the project they are about to undertake is well understood. The reality is that the more the V-Model is used as a tool to manage the software development process, the more likely that project is to fail. The following diagram is a typical representation of the V-Model. This model does have a number of good points, such as: It defines tangible phases of the process, and proposes a logical sequence in which these phases should be approached. However, this is as far as it goes. Let us take a look at the software development process for a moment. In the software development world, you can bet your last dollar that the plan will change. A second reason whey the V-Model fails, is in the testing phases, and has been illustrated by Brian Marick².