How do I treat application aspects with regard to features and user stories?
When drawing up a backlog, I have several requirements that apply to a great many user stories, i.e. aspects of the application like error handling and feedback. How do I include these (without using an #include directive in each user story )? Should I treat error presentation as a feature, then have user stories for this feature like “system catches exception, and shows info to user”?
Starting on a large project, should I split it into more concise parts?
Background: Currently an intern at a company and working on repurposing older programs (still in use, but for different departments) for use in testing new hardware. The new hardware is different in terms of register layout and firmware interface from the older iterations of hardware. I have been given free reign on how to setup this project as it is to be used for the new hardware exclusively.
How do I draft user stories as a developer?
I am writing a system where both the system owner and myself are developers, and we are currently the only source of ‘requests’ or requirements for the system, which I would like to capture in user stories tied to features{1}. My urgent priority now is to get a managaeble backlog captured. How should I go about capturing the level of technical spec I am used to to working with in users stories, which aren’t supposed to be too technical.
Is it better to find issues myself or let the computer figure it out?
I’m about to start the process of migrating a program from one component to another. Most of the core functionality will be the same but I’ll need to change database calls, etc. I’m sure there will be a few quirks somewhere.
Documentation degrading – how to deal with it?
Important: we have no issues whatsoever with source code documentation. This belongs to regular code audit and is kept up to date. Our problem is with developers documentation (or, “external” if you like), little blog-like tips from programmers to programmers which tend to be once written, often left behind.
BitBucket working with multiple developers on same project
I am new to BitBucket. I have my repository. And 2 people working on it me, Admin and another developer with Read only access.
Why can’t the IT industry deliver large, faultless projects quickly as in other industries?
After watching National Geographic’s MegaStructures series, I was surprised how fast large projects are completed. Once the preliminary work (design, specifications, etc.) is done on paper, the realization itself of huge projects takes just a few years or sometimes a few months.
How to implement a software development process in an existing project?
My question involves setting up a Software Development process. If you came in to an existing project that had no formal methodology or process set up, and then were asked to set one up yourself, how would you handle it? I have looked into various methodologies like Agile, or subsets thereof like XP, but these are primarily aimed at how to set up new projects. I am rather unsure how to implement them into an existing project.
Working on multiple things at work?
I was curious to know, if juggling between 2-3 projects at a time is a good or a common practice or not. When I say, 2-3 projects I mean:
1. 1 primary project,
2. 1 project with minor improvements/changes and
3. 1 project which comes at times for bug fixes
When, how and why should one upgrade (Java) frameworks?
Short summary as introduction: