…… 600 user stories in an application development backlog. All those user stories showed the team’s extensive due-diligence work in a complex project that involved a platform change. Unfortunately, having so many user stories was a sign of no consensus on goals
Avoiding too many user stories in software development
Although evolutionary, iterative and incremental development (IID) in software is in the ascendance as the modern or agile approach to replace ad hoc or waterfall (sequential lifecycle) development, its practiced and published roots go back surprisingly far. At least as far back as the mid 1950s, as a contemporary alternative to the nascent waterfall model …
Iterative and Incremental Development:A Brief History
Every Agile consultant is standing on shoulders of giants. In fact, we all are.
Upgrading php to php 5.5 (currently stable version)
- add-apt-repository ppa:ondrej/php5
- apt-get install python-software-properties
- apt-get update
- apt-get upgrade
- apt-get dist-upgrade
You do get option to replace your apache2.conf file, but I would select to keep your old version. In this instance, upon starting Apache, you MAY get error relating to httpd.conf and Lockfile statements. Just comment both of them out of apache.conf, and Apache will start fine.
Let me set something straight. Quality Assurance (QA) is about improving the process that is used to create the end result. In other words (in software development) the project lifecycle and all it’s inherent processes. The wikipedia defintion is not that bad, so there is no excuse for rebranding of QA as purely about testing (though testing processes do come under QA remit). To misunderstand what Quality Assurance probably means you don’t really understand what testing is about either. In other words, leave it to the experts. I realise saying we need to QA this product sound vaguely more exciting than we need to test this product. Reason being is that most people don’t get what it is anyway. Mysterious – hence, cooler.
Firstly, it is pervasive problem that too many people talking at length about Agile and testing that haven’t a clue what they are on about. The invasion of fashionable buzzwords to make the mundane sound more exciting, has become a tedious norm. There is much bandying about of “Lean” recently, with no consideration of the skills required to implement such projects. That’s an aside, but relevant also to automation. The word “automation” excites managers, as it implies efficiency. What it also implies is a possible nightmare.
… and why they shouldn’t have. It is relatively easy to see when and why some form of disillusionment occurred in testing world, after a few years of increasing hype around it. There were many healthy discussions around a tester’s place on modern Agile projects, and increased focus on test automation skills. It was when the context-driven school of testing put it’s hands up and fairly stated it could not be considered relevant. After all, what stays still in software development? The whole evolution is based on learning from mistakes, and improving programming. It is an interesting time, because once again testing has to reclaim it’s position, in the new surge of “testing is dead” mantras. Continue reading
At best, SCRUM is a sub-Agile method, which assumes all project memebers are dedicated, and in same location. The Product Owner is CRITCAL component on a SCRUM project. And this is where SCRUm can go awry – if the project has a Product Owner who is not sufficiently enaged with the project, or lacks skills to make good judgement calls on user stories.
Scrum is an Agile development framework that Jeff Sutherland invented at Easel Corporation in 1993. Jeff worked with Ken Schwaber to formalize Scrum at OOPSLA’95. Together, they extended and enhanced Scrum at many software companies and helped write the Agile Manifesto.