Agile Principles
March 12, 2007 by Anonymous
10 Key Principles of Agile Development
[censored out link]
Bookmark/Search this post with:
Permalink
- 31369 reads
Best of AgileSoftwareDevelopment.com
7 software development wastes
adoption
Agile
Agile 2008
bugs
change
communication
conference
contract
contracts
Daily stand-up
Development
done
efficiency
estimating
estimation
kanban
Kano
knowledge
lean
link
management
news
pair programming
people
photo
planning
planning poker
practice
presentation
principles
product backlog
product owner
project management
project planning
quality
requirements
retrospective
roles
Scrum
Self Organization
site
software
sprint
story points
Tampere
task board
TDD
team
testing
tool
user stories
user story
value
velocity
video
waste
weekly
XP
xp2007
- Scrum backlog templates and examples
- Simple Product Backlog Example
- Simple Sprint Backlog Example
- Our Story Board is Better Than Yours
- 10 Contracts for your next Agile Software Project
- Get Forum Nokia Support and Development Tools for Cheap
- Six Features of a Good User Story - INVEST Model
- Video tutorial: functional testing with Selenium IDE
- Top 20 Best Agile Development Books, Ever
- Video tutorial: Test Driven Development in practice
- 7 Tips for Improving the Daily Scrum
- Your Unit Tests Lie to You
- Top 10 Activities of the Product Owner
- Product backlog
- 10 Principles of Agile Project Time Management
- Video tutorial: Managing your Scrum Product Backlog with the help of a simple Excel sheet
- Five risks of solo programming
- Extreme Programming
- Video tutorial: Test Driven Development in practice
- 10 Signs That You're Not Agile
- Five steps for starting the Scrum project
- 10 Principles of Agile Project Time Management
- Destructive bonuses
Subscribe to updates
RSS feed
Subscribe on KindleNavigation
User login
Private blogs of the regular contributors
Comments
Censoring the empty posts out
March 12, 2007 by Artem, 5 years 10 weeks ago
Comment id: 101
Kelly, it's ok to post links to another agile-related resources on the forum. But wouldn't it be nice to add at least couple of sentences about it? What's behind the link? What's useful for this site visitors?
I am not able top view the
June 9, 2008 by tonydeepak, 3 years 49 weeks ago
Comment id: 1578
I am not able top view the post above... why??
See on the Kelly's blog
June 9, 2008 by Artem, 3 years 49 weeks ago
Comment id: 1579
Please visit my blog for a
July 18, 2008 by Anonymous (not verified), 3 years 44 weeks ago
Comment id: 1679
Please visit my blog for a survey regarding Agile practices in requirements engineering (which is closely related to Agile principles). I wish to know if Agile practices like acceptance test, requirements management tools, non-functional requirements, customer on-site and variable scope contracts are applicable in practice. Your help is much appreciated. The actual results may be interesting anyhow.
http://titylie.blogspot.com/
Real Worl Examples of Agile
August 17, 2008 by ZAKSHURST, 3 years 39 weeks ago
Comment id: 1786
Hi
I am looking fro some real world examples of Agile project in particular MSF 4.0 for development methodology combined with Scrums for management.
Background
Currently our company uses the water fall model, but new developments I believe are better suited to Agile. To this end I am trailing out Agile on a new project. The project is for a data centric application, with a multi deployment model. It is written VS2008 Vb.Net we are already design it to be test driven and starting to use NUNIT. I know Team system is supposed natural option but I find it difficult to justify based on the fact that most Open source seems to do a better job if less integrated and they have moved some functions from VS2008 into VSTS and now want us to pay for it. I can’t complain too much as VS2008 is fantastic tool
Anyway we are struggling with documentation , types required and level of detail required to keep the process streamline but also repeatable/ supportable. When looking there are hundreds if not thousands of articles on Agile and loads of templates, but I can’t find any real world examples,
• This is after 2 years of looking , lately the team has made it real priority to find examples but to no avail.
• being a Microsoft partner we have asked Microsoft directly but they can’t pin point any
• We have downloaded various trial software with supposed examples , but it is always templates.
• We have bought books that have said they have examples. I have hassled the authors.
I was hoping that end to end examples would be available, groups/people say they are working on them but it appears that they have been working on them for years. I thought competitions were held for best developments and I could get the examples from them.
I understand that you make agile your own and you have to tailor it to suit your needs, so examples are not useful but I need to see
- types and level of details that go into docs
- how information cascades from requiremenet,UAC, design to unit tests code etc.
- how you provide traceability
- how you provide auditable solutions, that show you have to external auditors how review and approval was performed.
For example I really hate documentation use of modelling diagrams and class digrams, properly source code is my aim but what should it look like. I really don’t want to repeat the mistakes and pitfalls others fall in. ( I am really afraid we will fail not because of Agile but because we don’t have a complete project, sceptics reviewing it will find too many holes. )
I hope this makes sense.
Conference reports
August 17, 2008 by Artem, 3 years 39 weeks ago
Comment id: 1787
As for backlog examples - here are some were gathered by Bas Vodde. As for the other questions, there are indeed not many complete stories on the web, however you can find many real world examples in the experience reports published in the various Agile conference proceedings. For example, proceedings of the just finished Agile 2008 contain dozens of examples described in as much detail as the authors managed to express.
I would try asking local agile companies for a possibility of a visit or I would try visiting a local agile group/conference. Written experience reports are nice, but live discussion would add even more value. Then after reading and talking, hiring a coach to help with the transition phase is often a good idea - there are so many ways to misinterpret any method.
Post new comment