Software Development Linkopedia October 2013

Here is our monthly selection of interesting knowledge material on programming, software testing and project management.  This month you will find information about business analysis, Agile and Scrum in the large, test automation, creating good user experience (UX) as a developer, legacy systems, distributed databases and the prioritization of your …

Software Development Linkopedia September 2013

Here is our monthly selection of interesting knowledge material on programming, software testing and agile or traditional project management.  This month you will find information about Scrum, software testing and how to be a software tester in a Scrum team. This month pointers also look a business analysis and documentation.

Writing More Than Code in Software Development

The recent trend in software development has been to produce less documentation and writing material. Many developers have interpreted the Agile Manifesto preference of “working software over comprehensive documentation” as the authorization to stop producing any document during a project. This has been translated in sentences like “the code is …

Software Development Linkopedia August 2013

Here is our monthly selection of interesting knowledge material on programming, software testing and agile or traditional project management.  This month you will find information about the skills of software testers and how they could pair with developers in an Agile setting. You will also explore the Cumulative Flow Diagram …

Software Development Linkopedia March 2013

Here is our monthly selection of interesting knowledge material on programming, software testing and project management: Blog: Supporting Fast-Moving Business Requirements Using Approval Branching Blog: Cynical Agile and Scrum Dictionary Blog: Real-time QA: staying confident with code Blog: Ten Things I Hate About Object-Oriented Programming Article: The Estimation Net Article: …

Software Could be the Least Important Result of a Project

“[Deliverables] is the least important level of an impact map. Don’t try to make it complete from the start. Refine it iteratively as you deliver. Treat deliverables as options, don’t take it for granted that everything listed here will actually be delivered. Don’t go into a lot of details early …