Take the 2-minute tour ×
Programmers Stack Exchange is a question and answer site for professional programmers interested in conceptual questions about software development. It's 100% free, no registration required.

I'm about to start on a project which will involve developing prototype native mobile apps (iOS and Android initially) as well as a web-based admin interface and an API for these apps to communicate with. We've got a list of stories already drafted up, however a lot of them are in the format:

As a mobile user I want to be able to view a login screen so that I can sign into the app

If this were targeted for a single platform, I wouldn't see a problem. However, since we're targeting multiple platforms, I'm not sure whether these should now be duplicated eg "As an Android user" or similar. This seems like duplication, but it's work that will need to be completed separately for each platform.

This is the first mobile project we've gone native on - previously it was Phonegap and we lumped all stories in under "As a mobile user". Since essentially this was a web-based app wrapped in native code, this didn't present too much of an issue, but I'm conscious that wholly-native apps are a different ballgame!

share|improve this question
    
This isn't really specific to mobile -- it applies to a project that must be delivered on multiple platforms, like a PC and Linux, or various gaming consoles. Should the title be changed? –  kevin cline Mar 28 '13 at 18:59
add comment

2 Answers

up vote 2 down vote accepted

I don't see why you don't want to make separate user stories for each mobile application. Even though the stories sound similar, they have huge differences both from developers' and users' point of view.

If you're using a system like Jira, you could even create a separate project for each application. This approach is better especially if all applications are completely independent in terms of resources _ different developer(s), different computer resources, etc. It would be easier to make estimations for each of the tasks.

If you still don't want to make separate user stories, you could create tasks for each application under the same story. But this would be convenient if you develop all the applications simultaneously, so that every story would be completed almost at the same time.

share|improve this answer
    
Thanks - this confirmation is what I was looking for! –  richsage Oct 11 '12 at 7:31
    
You're welcome )) –  superM Oct 11 '12 at 11:02
add comment

(I asume you use scrum). If the product owner knows upfront that he/she will always prioritize the different mobile platforms equally. (Eg. because it is a company policy)

And if your user stories are small enough, so that your team can do at least four or five of them in a sprint.

Only then you should not split your mobile stories into a story per platform. Use the definition of done to state all expected platforms.

In all other cases: split the mobile stories per platform. There is absolutely nothing wrong with that.

share|improve this answer
    
Thanks Kris - I take your point about them being small enough, that's definitely something to bear in mind when splitting them out (or not, as the case may be!) :-) –  richsage Oct 11 '12 at 7:32
add comment

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.