Originally posted on QA Mindset:

03_CD_automated_acceptance_test_low-res

View original

Originally posted on Scrum Master:

Planning and estimating tasks in Scrum involves creation of User Stories, approval and estimation of User Stories, creation and estimation of tasks, and creation of Sprint Backlog. Creation of User Stories involves writing of User Stories and their related User Story Acceptance Criteria. User Stories are usually written by the Product Owner and are designed to ensure that the customer’s requirements are clearly depicted and can be fully understood by all stakeholders. The Product Owner, based on his or her interaction with the stakeholders, business knowledge and expertise, and inputs from the team, develops User Stories that will form the initial Prioritized Product Backlog for the project. The Prioritized Product Backlog represents the total sum of what must be completed for the project. The objective of this exercise is to create elaborated and refined User Stories that can be approved, estimated, and committed to by the Scrum Team. At…

View original 592 more words

dsearle:

Good overview and analysis of Lollipop 5.0

Originally posted on Agile Net'Up:

View original

dsearle:

Some really useful observations made here, logical but often overlooked!

Originally posted on Technical Software Testing:

It’s fairly safe to say that quite a lot of test automation efforts fail. It is also very safe to say that without test automation an agile team fails. So how can you make sure that while doing agile your test automation will not fail and thus your agile team will not fail? One of the ways to answer this question is by looking at why test automation often fails within agile environments.

When I am talking about test automation within this post, I am referring to testing that is done to reduce the amount of manual regression work, the so called functional test automation or automatic regression testing.

Moving target

Test automation quite often does not receive the attention it needs and deserves, also in agile teams. Quite some test automation efforts start off too late and without the appropriate preparation, resulting in organic test automation driven by a…

View original 838 more words

If you have ever wondered which is the best smartphone OS to use then look no further than this article from Digital Trends which takes a look at the key wins for each of the Mobile OS.

The article covers many angles, and rates the OS accordingly in areas such as:

  • Affordability
  • Interface
  • Apps
  • App Store Usability
  • Battery Life
  • Updates
  • Cloud backups
  • Security

providing a balance view and highlights the key features in each section that the others provide in comparison. Though the article is behind in terms of the new releases of Apple, it still shows some useful analysis.

Through my work with Sogeti, and indeed through the promotion of the Sogeti Studio, our on-demand mobile lab, keeping up with the demand in the market place is a key challenge to ensure existing apps are compatible with the advances in devices and OS.

With the imminent release of iOS 8.1 due later this month and the suggested launch of Apple Pay; mobile decisions and utilisation of the features by businesses and app designers will provide another important rung on the mobile device market share ladder.

Good overview by Brian Wernham in his blog http://brianwernham.wordpress.com/2013/07/29/axelos-the-biggest-shake-up-in-project-management-good-practice-in-13-years/

More information available at http://axelos.gtml2.com/axeloslz/lz.aspx?p1=05735S1&CC&p=1&cID=0&cValue=1#building

And as outlined by Keith Richards (http://agilekrc.com) on day 1 of the Agile Business Conference in London, publications due for release in Q1 2015