Mee Proj Agile Methodology

[karna11]

[quote name='innovative' timestamp='1370825946' post='1303840262']

Np .. max methodology gurichi adagaru .. if adigithe(f2f iythe chances ekkuva) em vundhi cheppu ...

"maaku everday morning meeting vuntadhi and what we discuss is ninna em chesam, vatiki emanna issues vunnaya, what r the factors that r causing those issues n finally ivala em chestham "

confident ga cheppu convince avtharu ..
[/quote]
F2F, naa current Proj manger refer chesadu vere department lo proj ki

[ICANWIN]

[color=#000000]



[b] Agile Development Process[/b]

As opposed to the traditional waterfall method of software development, Agile development is about producing the simplest, quickest, most basic website and then rapidly evolving that website based on feedback from real users and their demonstrated needs.
Most organizations try to come up with every possible requirement on their wish list, drop it into a Request for Proposal (RFP), and then require a detailed project plan, crystal ball for the cost estimates, and a complete work breakdown structure (WBS) associated with milestone-driven payments. Agile doesn’t work this way. If this is what your organization needs, please consider the traditional method of web development.
Back to the top of [url="http://www.inqbation.com/agile-methodology-of-web-development/#top"]Washington DC agile developer[/url]

[b] Why use agile development methodology?[/b]

The agile development approach is very different from the traditional waterfall model in that the scope of work is not clearly defined up front. The reasons for working in an agile development model are primarily to:[list]
[*]Produce visible results quickly
[*]Create a proof-of-concept and early rapid prototype
[*]Get feedback from the target audience in order to guide future development
[*]Test different types of functionality and user experiences for best results
[*]Limit the risk and investment
[*]Start using the product as soon as possible
[*]Quickly iterate and evolve the product based on demonstrated user needs
[/list]
Back to the top of [url="http://www.inqbation.com/agile-methodology-of-web-development/#top"]Washington DC agile developer
[/url]
[b] Agile minimizes risk[/b]

If you are uncertain if your project is going to be successful or not then an agile approach is the better way to mitigate risk because it allows you to test the concept, get feedback and guidance from target users, and change priorities or direction during the process. You can also cut your losses early if you realize the product has no market feasibility or user demand.
With the traditional waterfall development approach, change orders are discouraged and costly because it requires a significant amount of documentation, clear and specific standards of acceptance, significant amount of time refining estimates, and changes to the contract or task order.
With agile, change is encouraged because it usually means that you have discovered an important requirement that you did not know before – or that a requirement is no longer needed and should not be developed further.
With agile development, you do not wait for the design to be completed until you move onto development. You actually design and develop simultaneously, fostering a form follows function approach to elegant design. You don’t wait until the entire project is over to test the system. You test as you go, train as you go, deploy as you go, and get feedback as you go. If the project ever loses funding or leadership, you will have working legacy software because we only take on as much work as we know we can finish.
Back to the top of [url="http://www.inqbation.com/agile-methodology-of-web-development/#top"]Washington DC agile developer
[/url]
[b] Lean Startup = Agile Development[/b]

There is a movement going on in the high-tech world called [url="http://theleanstartup.com/"]Lean Startup, which is based very much on the needs-driven development approach. With agile development, it is very much a needs-driven approach. We start off with 2 or 3 of the most important needs in the wish list, define them very well, build them, test them, deploy them, and get feedback on them before moving on to the next set of needs. The agile development approach ensures that the project meets current needs.
Back to the top of [url="http://www.inqbation.com/agile-methodology-of-web-development/#top"]Washington DC agile developer[/url]
[/url]
[b] Agile contracts[/b]

Agile development emphasizes customer collaboration over contract negotiation.
Agile works on a pure time and materials basis. From a cost perspective, there is uncertainty because the makeup of the team could change from sprint to sprint. Because we don’t have all the requirements up front, it is difficult to estimate the entire project costs in advance or the rate of development. Effective agile development requires total transparency to work.
With the traditional waterfall model of software development, you typically spend months specifying requirements, then months defining the user acceptance test plan, then months developing the code, then months designing the user interface, then months testing the code, and then months debugging the code, etc. By the time you are done, if you the project hasn’t run out of cash, the finished product is often obsolete or fails to meet expectations because end users were not involved in the process and didn’t give their feedback along the way.
Agile development, on the other hand, performs these tasks in parallel. With agile we plan, analyze, design, develop, document, and test simultaneously and iteratively. And, we invite user groups to steer development by being part of the process.
Back to the top of [url="http://www.inqbation.com/agile-methodology-of-web-development/#top"]Washington DC agile developer
[/url]
[b] Focus on results and low-hanging fruit[/b]

With agile, we deliver products early and often by demonstrating working software and getting acceptance along the way. We document as we go, train as we go, deliver as we go, and get feedback as we go. We use cross-functional teams including designers, developers, usability specialists, business analysts, quality assurance professionals, and team leaders to create a strong fabric of skills and abilities.
Agile development avoids excessive documentation and requirements specifications up front, preferring instead to specify and analyze only enough details to plan the next 2-3 week sprint, while keeping the ultimate road map and wish list set off to the side.
A common misunderstanding about agile is that we don’t document or plan when in fact we tend to invest more time and energy in planning and documenting because the plan is always evolving. We are always revisiting and revising the plan based on the continuous feedback loop we get from our client and the ultimate web visitors.
Being agile means providing a flexible process that anticipates and embraces change, allowing the team to adapt to evolving requirements and unexpected developments or priorities.
Back to the top of [url="http://www.inqbation.com/agile-methodology-of-web-development/#top"]Washington DC agile developer
[/url]
[b] Agile principles:[/b]
[list]
[*]Deliver usable website components early and continuously.
[*]Welcome changes to scope of work throughout the process.
[*]Keep sprints short and frequent, preferably in weeks, not months.
[*]Use cross-functional teams with a variety of business and technical skills.
[*]Meeting face-to-face meetings or web-conference, at least once a week.
[*]Provide daily communications and status updates.
[/list]
Back to the top of [url="http://www.inqbation.com/agile-methodology-of-web-development/#top"]Washington DC agile developer
[/url]
[b] Problems with Agile development methodology[/b]

The problem is that many people say they want Agile but don’t really understand how it works. Even worse, they don’t have the financial system, procurement system, contract system, or trust required to allow it to work.
Back to the top of [url="http://www.inqbation.com/agile-methodology-of-web-development/#top"]Washington DC agile developer
[/url]
[b] How agile development works[/b]

<a href="http://www.inqbation.com/wp-content/uploads/2012/07/agile-development-methodology-scrum1.jpg" style="text-decoration: none; color: rgb(32, 94, 123);" target="_blank">[img]http://www.inqbation.com/wp-content/uploads/2012/07/agile-development-methodology-scrum1.jpg[/img]
The way Agile works is that you have a Product Owner who represents the business unit that is financing the software development. This person has the vision and road map for what the ideal solution might be. Then you have the agile team, or the scrum team. The agile development team has a leader, often called the scrum master. The scrum master works with the product owner to develop and prioritize a wish list of features.
Then, the scrum master works with her developers to take a wild-assed guess, or perhaps educated guesstimates, of how long it will take to satisfy each wish on the list. They use this system of points and iterative debates among various members of the team. Truth is, nobody knows exactly how long it’s going to take to develop any piece of software. It’s always an estimate, it’s never an exact science.
The scrum master works with the Product Owner to define the functional tasks that will be completed during a relatively short sprint. Usually, sprints are a few days to a few weeks in length. Once this sprint is defined, then the teams blow out the details of the requirements, the work breakdown structure, the tasks, dependencies, required skills, and required team to design, develop, test, and deploy this limited set of functional requirements.
Sometimes, a software release may require a few sprints. But, the idea is that you don’t bite off more than you can chew. You don’t invest a lot of time defining, specifying, and analyzing a bunch of requirements that aren’t going to built during the upcoming sprint. And, everything you deliver works such that if you ever run out of funding, at least you’ve got a working set of functionality. You don’t want to, after all, have a half-finished Harley Davidson sitting in your garage taking up space. You either want to ride it or use that garage for other purposes.[/color]

[innovative]

[quote name='karna11' timestamp='1370825792' post='1303840257']
sprint anteee?, scrum antee?
[/quote]

sprint - fast ga chese small event
scrum - iterative approach ki ichina peru ..

own words lo cheppa .. correct def ante inka google cheyyi agile jargon ani

[ICANWIN]

nenu paste chesina 3 posts mastu karna to talk about agile methodology,..inka info kavalante cheppu i will look into and post few more..all the best

[ICANWIN]

[quote name='neopras' timestamp='1370825933' post='1303840261']

no its not, its a Agile project management tool..it can be used as bug tracking too..

its our enterprise standard tool for all projects..
[/quote]

ade kada vayya nenu cheppindi...agile tool kadu.. iPM tool ani...we use JIRA just as a PM tool though we are in agile env...water fall method lo work chesinappudu kuda in my prev proj i used Jira.

[vizagpower]

[quote name='ICANWIN' timestamp='1370826297' post='1303840276']
nenu paste chesina 3 posts mastu karna to talk about agile methodology,..inka info kavalante cheppu i will look into and post few more..all the best

[/quote]


needi ee tech dood?

[innovative]

[quote name='karna11' timestamp='1370826146' post='1303840271']
F2F, naa current Proj manger refer chesadu vere department lo proj ki
[/quote]

ante same company vere department ah

then they should have already known kada .. agile vaduthunnaro oo ledhoo..

[innovative]

[quote name='karna11' timestamp='1370826054' post='1303840268']
aa thread link anukuntaaa
[/quote]
oh okay ..

@ICANWIN : www.andhrafriends.com/topic/360365-only-pdfs-and-video-tutorials/

[ICANWIN]

edo oka satisfaction vachindi e roju kasta chaduvu gurinchi matlade dappadiki ..thanks to karna for ur thread...oka programming thread vesukoni andaram regular basis lo matladute bavuntundi..dont know how many are nterested

[vizagpower]

[quote name='innovative' timestamp='1370826474' post='1303840284']

ante same company vere department ah

then they should have already known kada .. agile vaduthunnaro oo ledhoo..
[/quote]

okasari pm check cheyava fleez!!!!!!!

[ICANWIN]

[quote name='innovative' timestamp='1370826513' post='1303840286']
oh okay ..

@ICANWIN : www.andhrafriends.com/topic/360365-only-pdfs-and-video-tutorials/
[/quote]


thanks inno for the informative thread link..

[ICANWIN]

[quote name='Ramakrishna_Bhai' timestamp='1370826451' post='1303840282']
needi ee tech dood?
[/quote]


java/j2ee

[innovative]

[quote name='ICANWIN' timestamp='1370826521' post='1303840287']
edo oka satisfaction vachindi e roju kasta chaduvu gurinchi matlade dappadiki ..thanks to karna for ur thread...oka programming thread vesukoni andaram regular basis lo matladute bavuntundi..dont know how many are nterested
[/quote]
[quote name='ICANWIN' timestamp='1370826621' post='1303840297']


java/j2ee
[/quote]

same here ..

already thread vundhi kada .. check out emanna helpful emo ... www.andhrafriends.com/topic/411946-javaj2ee-discussions

[innovative]

[quote name='ICANWIN' timestamp='1370826598' post='1303840294']


thanks inno for the informative thread link..
[/quote]

np ..

[ICANWIN]

[quote name='innovative' timestamp='1370826754' post='1303840304']
same here ..

already thread vundhi kada .. check out emanna helpful emo ... www.andhrafriends.com/topic/411946-javaj2ee-discussions
[/quote]

i never saw this thread..good one inno...ante nerrchukodaniki ani kaadu..learners freshers 1st time jobers kosam and we all can help them and answer their posts and simultaneously be in touch with what we learned....always active thread types...