Agile Software Development-Switching stories mid sprint
Introduction
Introduction
Nice list of meta skills to consider.
Is it on time? Under budget? Possibly these are the least important questions to worry about. This article offers a few other metrics to consider about regarding the value and purpose of a given project.
Short and sweet... and makes sense to me.
...where do requirements come from? They are analyzed into existence. Requirements are defined or created by the business analyst. The business analyst's job is to define the solution to a business problem. The requirements document is the representation of the complete and accurate statement of what must be done to solve the business problem. Requirements are a business analyst's job, not to gather, but to create.
This is likely to be useful for me in the near future.
Although written by a Drupal consultant, this is a great structure for any IT project.
Some very good ideas here for attendance guidelines...
On its face this article is about how to interview for a development job. But as a BA, this offers nice guidelines for many projects I have worked on.
«Just like medicine, if we don't approach things in a systematized way, and make sure we're incorporating all the different stakeholders, we're going to be in trouble. You can't just go out make a bunch of decisions on your own,» says Schumacher. IT pros must be able to shepherd users through business processes