Tag Archives: Agile Software Development Methodologies

Agile Environment

      What are the latest tools and techniques for requirements gathering in an Agile environment? Do you see any emerging trends? 

In Agile frequent delivery is required and scope of documentation is very less.
In Agile development module, the benefits of getting “continuous” feedback from client came into process. This leads to organizations to recognize the opportunity to continue gathering requirements throughout the process — refining, clarifying, and discovering new requirements.
But as in Agile changes are so frequent we need to keep track of all this. Due to this tools helps us a lot.
Tool:
Arbiter is a requirements gathering and verification tool for web projects. Its aim is to sharpen the communication between stakeholders and developers.
Technique:
A JAD(Joint Application Design) is a facilitated and highly structured meeting that has specific roles of leader, speaker, facilitator, participant and observer.  JADs have defined rules of behaviour including when to speak, and typically use a round or U-shaped table. Motive is to distribute a appropriate agenda and an information package which everyone is expected.  MOM(Minutes of Meeting) are written and distributed after a meeting, including a list of action items assigned during the JAD that the facilitator is responsible for ensuring are actually performed.Image
Advertisements

Leave a comment

Filed under Uncategorized

Agile Software Development Methodologies

Let’s have Project Managers share their opinion: Does test-driven development fall into project manager duties? 

With any project whatever methodology we may use like agile (XP, scrum…) or traditional (waterfall, spiral…) they all almost have same goal/target and phases.  Goal of providing guidelines/discipline for better, manageable software development; all methodologies have feasibility, planning, requirements, risk analysis,  closing of a project apart from design, development and testing phases but it’s just the way how they are implemented/maintained or outlined by that particular methodology. Planning, requirements, risk analysis, closing come under the umbrella of roles/responsibilities of project manager; he is the bridge between clients, company and people working on a project. TDD is one of the agile practices that facilitates robust, manageable and testable code upfront though it have its challenges,  even in TDD all the aspects of project management are present which cannot be neglected.Image

Leave a comment

Filed under Uncategorized

Agile Development

At QAIT DevLabs, we follow Agile development methodologies in all our software engineering efforts. We have adapted our agile practices in a way that best suits building products from scratch as well re-building or sustaining existing software products. Read further to know how our practices bring into play the below principles from the Agile Manifesto.

For more details, please log on to: – http://www.qaitdevlabs.com/AgilePractices.html

1 Comment

Filed under Uncategorized

Agile Software Development Methodologies

Agile software development methodologies are almost the same but they are different in terms of their terminology, practices, tactics and implementation standpoint. Agile methodologies follow lean and flexible approach as per the requirement. The various kind of methodologies being used are Scrum, lean and kanban software development, Extreme Programming(XP), Crystal, DSDM, FDD etc. To know more about these methodologies log on to:

http://www.qaitdevlabs.com/AgilePractices.html

Leave a comment

Filed under Agile Software Development Methodologies

Agile Software Development At QAIT DevLabs

At QAIT DevLabs, we follow Agile development methodologies in all our software engineering efforts. We have adapted our agile practices in a way that best suits building products from scratch as well re-building or sustaining existing software products. Read further to know how our practices bring into play the below principles from the Agile Manifesto.

Implementing Agile Manifesto

“Satisfy the customer through early and continuous delivery of valuable Software. Deliver working Software frequently, from a couple of weeks to a couple of months, with a preference for the shorter timescale”

Every project starts with a master planning that determines high level features for the product, best estimates and mapping/splitting them into small releasable chunks. These chunks are short development/QA efforts labeled as a Sprint. Typically we prefer a 2 week Sprint schedule. Every Sprint starts with a planning meeting that outlines a clear path to achieve the deliverables over the duration of the Sprint. Meticulous planning taking into account backlogs, and expecting unknowns along with daily tracking ensures that we never deviate from the plan.

Leave a comment

Filed under Agile Software Development Methodologies