topic Re: Can anyone Explain me Ajile Method? in QlikView

Can anyone Explain me Ajile Method?

Fri, 05 Jun 2015 09:38:59 GMT

Hi all,

Can anyone tell me agile method, How it's work? Why? requirements?

Ramaya.

Re: Can anyone Explain me Ajile Method?

Peter_Cammaert — Fri, 05 Jun 2015 09:40:57 GMT

Wikipedia can: Agile software development - Wikipedia, the free encyclopedia

Edit: OK this one got stuck in Moderation from 11:40 til 17:17 local time. Thanks guys.

Re: Can anyone Explain me Ajile Method?

swuehl — Fri, 05 Jun 2015 09:42:09 GMT

Agile software development - Wikipedia, the free encyclopedia

Re: Can anyone Explain me Ajile Method?

jyothish8807 — Fri, 05 Jun 2015 09:42:21 GMT

Hi Ramya,

Are you looking for the this?

http://agilemethodology.org/

Regards

Re: Can anyone Explain me Ajile Method?

qlikmsg4u — Fri, 05 Jun 2015 09:43:31 GMT

Just google it, you will find tons of information about Ajile Methodology.

https://www.google.co.in/webhp?sourceid=chrome-instant&ion=1&espv=2&ie=UTF-8#q=agile%20methodology

Re: Can anyone Explain me Ajile Method?

jyothish8807 — Fri, 05 Jun 2015 09:43:55 GMT

Hi Ramya,

Agile Methodology

What Is Agile?

The Agile movement proposes alternatives to traditional project management. Agile approaches are typically used in software development to help businesses respond to unpredictability.

What is Scrum?

The Scrum Reference Card

Scrum is the most popular way of introducing Agility due to its simplicity and flexibility. Because of this popularity, many organizations claim to be “doing Scrum” but aren’t doing anything close to Scrum’s actual definition. Scrum emphasizes empirical feedback, team self management, and striving to build properly tested product increments within short iterations. Doing Scrum as it’s actually defined usually comes into conflict with existing habits at established non-Agile organizations.

Scrum has only three roles: Product Owner, Team, and Scrum Master. These are described in detail by the Scrum Training Series. The responsibilities of the traditional project manager role are split up among these three Scrum roles. Scrum has five meetings: Backlog Grooming (aka Backlog Refinement), Sprint Planning, Daily Scrum (aka 15-minute standup), the Sprint Review Meeting, and the Sprint Retrospective Meeting.

Many books and classes are available from a variety of competing sources of varying accuracy and quality. One place to start would be the Scrum Training Series, which uses an entertaining approach to cover the most popular way of introducing Agile to teams. You can also download the 6-page illustrated Scrum Reference Card.

What’s Wrong With Traditional Approaches?

In 1970, Dr. Winston Royce presented a paper entitled “Managing the Development of Large Software Systems,” which criticized sequential development. He asserted that software should not be developed like an automobile on an assembly line, in which each piece is added in sequential phases, each phase depending on the previous. Dr. Royce recommended against the phase based approach in which developers first gather all of a project’s requirements, then complete all of its architecture and design, then write all of the code, and so on. Royce specifically objected to the lack of communication between the specialized groups that complete each phase of work.

It’s easy to see the problems with the waterfall method. It assumes that every requirement can be identified before any design or coding occurs. Could you tell a team of developers everything that needed to be in a software product before any of it was up and running? Or would it be easier to describe your vision to the team if you could react to functional software? Many software developers have learned the answer to that question the hard way: At the end of a project, a team might have built the software it was asked to build, but, in the time it took to create, business realities have changed so dramatically that the product is irrelevant. Your company has spent time and money to create software that no one wants. Couldn’t it have been possible to ensure the end product would still be relevant before it was actually finished?

Today very few organizations openly admit to doing waterfall or traditional command and control. But those habits persist.

Why Agile?

Agile development provides opportunities to assess the direction throughout the development lifecycle. This is achieved through regular cadences of work, known as Sprints or iterations, at the end of which teams must present a potentially shippable product increment. By focusing on the repetition of abbreviated work cycles as well as the functional product they yield, agile methodology is described as “iterative” and “incremental.” In waterfall, development teams only have one chance to get each aspect of a project right. In an agile paradigm, every aspect of development — requirements, design, etc. — is continually revisited. When a team stops and re-evaluates the direction of a project every two weeks, there’s time to steer it in another direction.

This “inspect-and-adapt” approach to development reduces development costs and time to market. Because teams can develop software at the same time they’re gathering requirements, “analysis paralysis” is less likely to impede a team from making progress. And because a team’s work cycle is limited to two weeks, stakeholders have recurring opportunities to calibrate releases for success in the real world. Agile development helps companies build the right product. Instead of committing to market a piece of software that hasn’t been written yet, agile empowers teams to continuously replan their release to optimize its value throughout development, allowing them to be as competitive as possible in the marketplace. Agile development preserves a product’s critical market relevance and ensures a team’s work doesn’t wind up on a shelf, never released.

Regards

Re: Can anyone Explain me Ajile Method?

Peter_Cammaert — Fri, 05 Jun 2015 09:44:59 GMT

Moderation will cause a lot of identical answers to queue up without anyone knowing. Necessary evil?

Re: Can anyone Explain me Ajile Method?

swuehl — Fri, 05 Jun 2015 09:50:42 GMT

Is moderation still on?

Haven't seen this message for a while, but usually I try to remove the hyperlinks from external site references (...not in above post).

Moderated discussions?

Re: Can anyone Explain me Ajile Method?

Peter_Cammaert — Fri, 05 Jun 2015 09:59:08 GMT

In the mean time, I was thinking in the opposite direction: I still get moderation lockdowns, so you probably escaped moderation altogether (which is perfectly fine by me, something all Legends should get). I was wondering whether I can get this privilege at 25k or 50k points...

Re: Can anyone Explain me Ajile Method?

Peter_Cammaert — Fri, 05 Jun 2015 10:47:09 GMT

Doh, Toni Kautto comes in and marks your answer as correct while mine is still in moderation.If he's the moderator then this means he doesn't like me...

Re: Can anyone Explain me Ajile Method?

jyothish8807 — Fri, 05 Jun 2015 11:20:12 GMT

Mine is also under Moderation This means he doesn't like me also.

Re: Can anyone Explain me Ajile Method?

Peter_Cammaert — Fri, 05 Jun 2015 12:28:51 GMT

Well I guess moderators are taking a nap.

Re: Can anyone Explain me Ajile Method?

jyothish8807 — Fri, 05 Jun 2015 12:40:02 GMT

Hahaha... May be. Moderators i am a good guy.. don't doubt me

Re: Can anyone Explain me Ajile Method?

Fri, 05 Jun 2015 12:48:07 GMT

I'll try to briefly explain what Agile Methodology is...

In Agile Methodology, a project is broken down into multiple Sprints. Sprints can be of a week, 2 weeks, 3 weeks or more (this is flexible). In a sprint each team member will have specific tasks to work on. These tasks can be anything like development of code, report building, testing etc. Every day (not more than 15 minutes) you will have a Scrum meeting where in all team member will come together and a Scrum Master (one of the team member) will ask each member the following 3 questions:

1. What have you been working on?

2. What will you be working on?

3. Are there any obstacles/roadblocks?

Also there will be a white board in front of the team on which Yellow stick-ons (well can be of any color) will be sticking and each will have a single task written on it. A team member can pick a task if he/she is done with their originally assigned task. This is why this methodology is called an Agile methodology because everything moves quickly and all team members get to work on different areas of the project.

Please do read online other articles about Agile Methodology. Hopefully mine gives a brief overview.

Thanks,

Vidit

Re: Can anyone Explain me Ajile Method?

Peter_Cammaert — Fri, 05 Jun 2015 15:27:02 GMT

I edited my original post to add the moderation timestamps (6 hrs). Now it's stuck again in moderation