The Meaning of Agile Certification is Money

Published January 9th, 2012 Under Software Development | 2 Comments

On page 483 of their book ” Practices for Scaling Lean & Agile Development“, Craig Larman and Bas Vodde discuss about the quality of code and certification, mainly in within the CMMI context. They refute the link between good code production and certification and wrote “Do not believe that an appraisal, rating, or certification in any process improvement model – including Scrum, agile methods and ISO certification – means much of anything, other than the ability to somehow pass an appraisal at least once.”

Although I usually agree with them, I would disagree on this point. Certification has its meaning. And this meaning is money. Certification has become an important business and this is why you have so many “independent” professional associations that now provide some type of certification. In the Agile project management world, you can be
* a certified ScrumMaster from the Scrum Alliance
* a Professional ScrumMaster from Scrum.org
* a PMI Agile Certified Practitioner from the Project Management Institute (PMI)

In addition, you can now become a certified Agile tester or Product Owner. I am myself planning to create a Certified Agile Blogger status. Read more

Agile Culture, Scrum, User Experience and Software Architecture in the Winter 2011 issue of Methods & Tools

Published December 21st, 2011 Under Methods & Tools | Leave a Comment

Methods & Tools – the free magazine for software developers, testers and project managers – has just published its Winter 2011 issue with the following articles that focuses mainly on agile project management, software architecture and user experience. In addition, four open source software development tools are presented, two for software testing and two for project management. Winter 2011 issue content:

* How to Make Your Culture Work with Agile, Kanban & Software Craftsmanship
* How Software Architecture Learns
* Understanding of Burndown Chart
* The Psychology of UX – Part 2
* Cucumber: Behavior Driven Development in Ruby
* Sureassert Exemplars: Java Unit Testing Without Unit Tests
* ChiliProject: Modular Open Source Web-based Project Management
* Scrum-it: Virtual Open Source Scrum Board Application

70 pages of software development knowledge that you can download from http://www.methodsandtools.com/mt/download.php?winter11

Software Development Linkopedia December 2011

Published December 7th, 2011 Under Links | Leave a Comment

Web Site: The Twelve-factor Applications

Web Site: Selenium Tutorial

Blog: Please help Jenkins pay the project expense

Blog: Create the Place Where You Long to Belong

Article: The End of Projects: Moving Toward Evidence-Based Software Investment

Article: NoSQL Databases and Node.js

Article: Unit Testing in Java: A Sleeping Snail

Article: Develop applications using a collaborative, user-centric model

Article: But We Have These Distributed Folks

Tool: The Dart language

Tool:  Glimpse – Debug your .NET server

Podcast: Distributed Scrum

Video: Functional Software Testing Tool Selection

Video: Scaled Agile Framework

Video: Java and NoSQL in the Real World

Video: How We Do Language Design at Microsoft

Find more interesting knowledge and content on the software development resources directory, the software development tools directory, the software development articles directory, the software development blogs aggregator or the software development videos directory.

Software Linkopedia November 2011

Published November 16th, 2011 Under Links | Leave a Comment

Here is our selection of interesting knolwedge material on programming, software testing and project management:

Web site:  SymbolHound a search engine for programmers and coders

Blog: More about distributed Scrum – one example

Blog: Dan North at Oredev: Embrace Uncertainty

Blog: How Mature Is Your Continuous Integration?

Article: Understanding the Concept of the Minimum Viable Product (MVP)

Article: Design Peer Reviews the ATAM Style

Article: Building the Right Scope

Article: MongoDB vs. RDBMS Schema Design

Tools: Robolectric – Test-Drive Your Android Code

Tool: Spinach – a BDD framework that features encapsulation and modularity

Video: Secrets of World Class Software Organizations

Video: Software Testing is Dead

Video: Successful Agile Planning: An Iteration How-to

Video: Metrics for Better Software Teams

Video: Java Security Trends

Find more interesting knowledge and content on the software development resources directory, the software development tools directory, the software development articles directory, the software development blogs aggregator or the software development videos directory.

What is a Successful Software Project?

Published September 28th, 2011 Under Software Development | Leave a Comment

Recently somebody asked on a forum “when is Scrum not working?” This lead me to the question “when is a project successful?” Traditionally, you can measure the success of a project by checking the respect of the scope, schedule and budget at the delivery of the application. In this situation, the burden is more on project managers and developers: they have to estimate the user requests and deliver on these estimates. This requires the mostly complete definition of the requirements at the beginning of project. Every change is the subject to negotiation as it could cause a change in either the budget or the schedule. In this situation, people might be more judging the capacity of people to estimate… or better to protect themselves from unexpected problems. I am sure that many of you have heard: “Take your initial estimate and multiply them by two before communicating them to your project manager or end-user”. A more business-oriented definition of a successful project is based on the delivery of value, the faster the better. In this case, the success of a project could normally be assessed only after the delivery of the application, assessing its return on investment (ROI). The concept of business value might be also implicitly present in the traditional project approach, but its mindset is more strictly focused on the project management results than the creation of value. Read more

keep looking »