topsyWidgetPreload({ “url”: “http%3A%2F%2Ftynerblain.com%2Fblog%2F2006%2F09%2F29%2Fburndown%2F”, “style”: “big”, “title”: “Burndown Bullied Into Business Analysis” }); Burndown is a technique used in Scrum projects for tracking the progress within or across sprints. It is an exciting way to track how a team is progressing against a deadline – and we can apply it to any form of project-status. In [...]
Category Archives: Process Improvement
Posted in Agile, Business Analysis, Process Improvement, Project Management, Requirements gathering
Tagged burndown, burndown requirements gathering, managing data, measuring requirements analysis, reporting, reporting requirements, requirements analysis reporting, requirements status, scrum, status reporting, tracking requirements, tracking status
2 Comments
Making Agile Offshore Teams Work
Agile processes stress communication and colocation. Splitting a team into on and offshore resources inhibits the first and prevents the second. Teams struggle to resolve this apparent conflict of interest. Applying best practices (for any team) to address these challenges makes it possible. Martin Fowler provides us with great guidance based on years of experience with his company.
Quick Thoughts on Incremental Project Management
topsyWidgetPreload({ “url”: “http%3A%2F%2Ftynerblain.com%2Fblog%2F2006%2F07%2F25%2Fincremental-project-mgmt%2F”, “style”: “big”, “title”: “Quick Thoughts on Incremental Project Management” }); Incremental delivery planning is not an oxymoron. You just plan the soon-to-happen tasks in detail, and keep the distant tasks more vague. Does this make sense? Rolling-Wave Planning Johanna Rothman has posted an article that provides a good introduction to rolling-wave planning. [...]
Companies Will Waste $1B This Year on Software Tools
Gartner reported that companies spent $3.7 Billion USD on application development tools in 2004, with a 5% annual growth rate. The Standish Group has shown that 40% to 60% of project failures are due to requirements failures. At least 1/3 of the money spent on getting more efficient at coding is being wasted – it should be spent on writing the right software.
Non-Functional Requirements Equal Rights Amendment
We know how to deal with functional requirements. We know they are important – we can walk the dependency chain from goals to use cases to functional requirements. But how do we get to the non-functional requirements? Leathej1 points out the elephant in the room – non-functional requirements don’t get enough attention when it comes to testing. Let’s look into it some more…
Posted in Process Improvement, Requirements, Software development, Testing
Tagged constraint, functional requirements, goal, karl wiegers, managing data, non-functional requirements, requirement, requirements management, software process, software product success, structured requirements, use cases
12 Comments
Foundation Series: Functional Testing of Software
Functional Testing, also referred to as System Testing of software is the practice of testing the completed software to confirm that it meets the requirements defined for the software. A functional test is typically a test of user interactions, but can also involve communication with external systems. We contrast functional testing with unit testing. We also show how functional testing provides different benefits than unit testing.
Posted in Agile, Foundation series, Process Improvement, Software development, Test Automation, Testing
Tagged automated testing, black box testing, blackbox testing, blackbox tests, functional testing, functional tests, graybox testing, graybox tests, keyword table testing, managing data, qtp, software development process, software process, software product success, software quality, system testing, testing automation, unit testing, white box testing, whitebox testing, whitebox tests, winrunner
6 Comments
Latest Articles
Comments on all Articles
