innovative Posted June 10, 2013 Report Posted June 10, 2013 [quote name='ICANWIN' timestamp='1370825477' post='1303840244'] Jira is a bug tracking tool...need not necessarily agile envi to use it ...correct me if i am wrong [/quote] u r right .. not necessarily agile .. but ppl use it as proj management tool also ...
ICANWIN Posted June 10, 2013 Report Posted June 10, 2013 [quote name='karna11' timestamp='1370825552' post='1303840248'] REPU INTERVIEW VUNDHI, VALLA REQUIREMNET AGILE VUNDHI, NENU NAA CURRENT PROJ AGILE ANI PETTAA BUT NAA CURRENT AGILE KADHU NAA PROJ AGILE ANI ELA CONVIENCE CHEYYALII ANI [/quote] Any agile env same padhathi..agile env ala work avutundo telusuko..its only a methodology not technology ...asalento teluste emaina vagi convince cheyachu irrespective of project
ICANWIN Posted June 10, 2013 Report Posted June 10, 2013 [quote name='innovative' timestamp='1370825631' post='1303840250'] u r right .. not necessarily agile .. but ppl use it as proj management tool also ... [/quote] I thought so too
karna11 Posted June 10, 2013 Author Report Posted June 10, 2013 [quote name='innovative' timestamp='1370824402' post='1303840210'] maadhi agile eh karna .. emundhi roju standup vuntadhi .. ante evaru em chesaro update ivvali .. and oka board maintain chestharu .. dhanlo stages of every sprint ni columns ga rastaru. basically anni tasks ni rastharu first column lo then sprint days jaruguthu vunna time lo every day meeting vundadhi kada .. vatillo emanna task complete iynattu anipisthe .. you can move that task to next specified column .. simple ga cheppali ante hadavidi ga project cheyyatam... details ante em kavalo particular ga adugu.. naaku thelisthe cheptha [/quote] sprint anteee?, scrum antee?
ICANWIN Posted June 10, 2013 Report Posted June 10, 2013 [quote name='karna11' timestamp='1370825792' post='1303840257'] sprint anteee?, scrum antee? [/quote] google lo kottavayya...avi type chesi explain cheyadam kashtam...let me look for a link for u
vizagpower Posted June 10, 2013 Report Posted June 10, 2013 [quote name='karna11' timestamp='1370822850' post='1303840179'] naa, ithee koncham details gaa cheppandi babu em jaruguthundhii agile looo day to day task ela discuss chestharooo plzz thanks in advance [/quote] ee tech karna????
ICANWIN Posted June 10, 2013 Report Posted June 10, 2013 [b] What is Agile?[/b] [color=#686868][font=Arial, Helvetica, sans-serif][size=3] Agile methodology follows an iterative approach in the development of the software. This helps to minimize the overall risk, and allows the project to adapt to changes quickly and does not require a requirements freeze upfront. Work is carried out in iterations, which typically last one to six weeks.[/size][/font][/color][color=#686868][font=Arial, Helvetica, sans-serif][size=3] [img]http://www.innolance.com/sites/all/themes/framework/images/delivery_agile.gif[/img] Agile development methods emphasize effective communication over written documents. The Project requirements are well documented upfront. Then, depending upon business priority, these features are assigned to releases, which are tied to iterations. Each agile team will contain a customer representative.[/size][/font][/color] [color=#686868][font=Arial, Helvetica, sans-serif][size=3] Agile development methods emphasize working software as the primary measure of progress. There are several popular agile methodologies like Scrum and Extreme Programming (XP). One of the fundamental ideas of XP is that not one process fits every project, but rather, practices should be tailored to the needs of individual projects. Almost all agile methods are suitable for method tailoring. We create a customized process for each client, taking his specific needs into account. We understand the importance of customization when it comes to client requirements.[/size][/font][/color] [url="http://www.innolance.com/process#agile"][Back to top][/url] [b] Why Agile?[/b] [color=#686868][font=Arial, Helvetica, sans-serif][size=3] As of 2009, the waterfall model is still in common use. Progress is generally measured in terms of deliverable artifacts: requirement specifications, design documents, test plans, code reviews and the like.[/size][/font][/color] [color=#686868][font=Arial, Helvetica, sans-serif][size=3] The main problem with the waterfall model is the inflexible division of a project into separate stages, so that commitments are made early on, and it is difficult to adapt to changes in requirements. This means that the waterfall model is likely to be unsuitable if requirements are not well understood or are likely to change in the course of the project. The waterfall model is bureaucratic, slow, demeaning, and inconsistent with the ways that software developers actually perform effective work.[/size][/font][/color] [color=#686868][font=Arial, Helvetica, sans-serif][size=3] Agile development methods produce completely developed and tested features of a small subset of the project once in every few weeks. The emphasis in Agile methodology is on obtaining the smallest workable piece of functionality to deliver business value early, and continually improving it and adding further functionality throughout the life of the project.[/size][/font][/color] [url="http://www.innolance.com/process#agile"][Back to top][/url] [b] Why other methodologies fail:[/b] [list] [*]Lack of end-user (customer) involvement [*]Poor requirements [*]Unrealistic schedules [*]Lack of change management [*]Lack of testing [*]Inflexible and bloated processes [/list] [url="http://www.innolance.com/process#agile"][Back to top][/url] [b] Why is Agile successful?[/b] [list] [*]The web-based model allows companies to launch a bare bones version of the product first, get feedback from end-users and then incrementally add new features based on that feedback. [*]Products have to be developed with the latest technologies in a short time frame incorporating the need to changes so that the product is not outdated by the time of launch. [*]Agile may not address every software development problem, but it is a very profound step in the right direction. [/list][color=#686868][font=Arial, Helvetica, sans-serif][size=3] It makes a serious attempt at addressing many of the key problems with current software development processes by empowering and respecting the people who are part of the process and by taking a pragmatic and realistic approach to the software development business. In this respect, agile critics may assert that these features are not placed in context of the overall project, concluding that, if the sponsors of the project are concerned about completing certain goals with a defined timeline or budget, agile may not be appropriate. Proponents of agile development counter that, adaptations of Scrum show how agile methods are augmented to produce and continuously improve a strategic plan.[/size][/font][/color] [url="http://www.innolance.com/process#agile"][Back to top][/url] [b] What is SCRUM?[/b] [color=#686868][font=Arial, Helvetica, sans-serif][size=3] Scrum is an iterative incremental process of software development commonly used with agile software development. It is the default process we use. Scrum can be implemented at the beginning of a project or in the middle of a project or product development effort that is in trouble -often within thirty days.[/size][/font][/color] [color=#686868][font=Arial, Helvetica, sans-serif][size=3] Scrum is a set of interrelated practices and rules that optimize the development environment, reduce organizational overhead, and closely synchronize market requirements with iterative prototypes. Based on modern process control theory, Scrum causes the best possible software to be constructed given the available resources, acceptable quality, and required release dates. Useful product functionality is delivered every thirty days as requirements, architecture, and design.[/size][/font][/color] [color=#686868][font=Arial, Helvetica, sans-serif][size=3] A key principle of Scrum is its recognition that during a project the customers can change their minds about what they want. Scrum accepts the fact that no problem can be fully understood or defined and hence focuses on maximizing the team's ability to deliver quickly and respond to emerging requirements. One of Scrum's biggest advantages is that it is very easy to learn and requires little effort to start using.[/size][/font][/color]
neopras Posted June 10, 2013 Report Posted June 10, 2013 [quote name='ICANWIN' timestamp='1370825477' post='1303840244'] Jira is a bug tracking tool...need not necessarily agile envi to use it ...correct me if i am wrong [/quote] 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..
innovative Posted June 10, 2013 Report Posted June 10, 2013 [quote name='karna11' timestamp='1370825552' post='1303840248'] REPU INTERVIEW VUNDHI, VALLA REQUIREMNET AGILE VUNDHI, NENU NAA CURRENT PROJ AGILE ANI PETTAA BUT NAA CURRENT AGILE KADHU NAA PROJ AGILE ANI ELA CONVIENCE CHEYYALII ANI [/quote] 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 ..
ronitreddy Posted June 10, 2013 Report Posted June 10, 2013 [quote name='karna11' timestamp='1370825792' post='1303840257'] sprint anteee?, scrum antee? [/quote] http://searchsoftwarequality.techtarget.com/definition/Scrum-sprint
karna11 Posted June 10, 2013 Author Report Posted June 10, 2013 [quote name='Ramakrishna_Bhai' timestamp='1370825923' post='1303840259'] ee tech karna???? [/quote] .Net
innovative Posted June 10, 2013 Report Posted June 10, 2013 [quote name='ICANWIN' timestamp='1370825584' post='1303840249'] INno can you share that pdf...may be future lo useful avvachu just want to have a look...thanks in advance [/quote] particular ga em pdf cheppu ...
ICANWIN Posted June 10, 2013 Report Posted June 10, 2013 [b] Agile Methodology[/b] [color=#4D4D4D][font=Verdana, Arial, Helvetica, sans-serif][size=3]Traditionally software development projects have been managed in much the same was as physical engineering: a long planning stage, during which no code is produced but lots of plans are produced, is followed by an intense implementation phase, in which the plans are followed carefully to create the final product.[/size][/font][/color] [color=#4D4D4D][font=Verdana, Arial, Helvetica, sans-serif][size=3]When building a physical artifact, like a bridge, this methodology works well – everyone knows what the bridge is supposed to do, and the inflexibility of materials like poured concrete and steel means that once implementation is started, opportunities for change are extremely limited.[/size][/font][/color] [color=#4D4D4D][font=Verdana, Arial, Helvetica, sans-serif][size=3]Agile methodology makes use of the fact that software is a much more flexible material than physical construction to mitigate one of the primary problems with traditional software engineering – the customer is often not entirely sure of how the finished product should work until half-way through the implementation phase.[/size][/font][/color] [color=#4D4D4D][font=Verdana, Arial, Helvetica, sans-serif][size=3]The “Agile Manifesto” [sup][url="http://www.refractions.net/expertise/agile/#1"]1[/url][/sup] provides the following principles of project management.[/size][/font][/color][list] [*][b]Individuals and interactions[/b] over processes and tools [*][b]Working software[/b] over comprehensive documentation [*][b]Customer collaboration[/b] over contract negotiation [*][b]Responding to change[/b] over following a plan [/list] [color=#4D4D4D][font=Verdana, Arial, Helvetica, sans-serif][size=3]The agile principles recognize that software projects are subject to continuous change, both in terms of client expectations and underlying technology, in a way that traditional engineering projects are not, and that software has properties that allow different management techniques to be used.[/size][/font][/color][list] [*]A half-built bridge is probably non-functional. With an agile methodology a half-built piece of software can be functional and usable, at least for a subset of its expected functions. This allows agile methods to provide customers with “continuous delivery”, a working piece of software at very regular intervals. [*]A customer knows what a bridge will do from the start. A customer may change her conception of what a piece of software will do mid-stream, in response to being exposed to an interim delivery. Continuous delivery drives a process of continuous refinement of requirements. [*]A customer can only provide continuous refinement in the presence of good information about the progress of the project, the limitations of the underlying technology and other factors. Transparency of process and high levels of communication with the customer are key to an agile approach. [/list] [b] Scrum[/b] [color=#4D4D4D][font=Verdana, Arial, Helvetica, sans-serif][size=3]Refractions uses a particular agile methodology called "Scrum" [sup][url="http://www.refractions.net/expertise/agile/#2"]2[/url][/sup]. Scrum provides the planning tools to achieve the goals of the agile manifesto:[/size][/font][/color][list] [*][b]A product “backlog” of prioritized work to be done.[/b] The backlog is made up of easily-understood “user stories” that illustrate an increment of product functionality. [*][b]Completion of a fixed set of backlog items in a series of short two- to four-week iterations or “sprints”.[/b] The relative shortness of the sprints improves the transparency of the process and gives the development team regular and achievable goals. [*][b]A brief daily meeting or “scrum”, at which progress is explained, upcoming work is described and impediments are raised.[/b] The daily scrum is at the heart of the process, allowing management to understand and resolve issues before they become serious (and unnecessary) delays. [*][b]A brief sprint planning session in which the backlog items for the sprint will be defined.[/b] Much like a traditional planning process, but more effective because of the smaller development increment – there is less opportunity for error because the delivery is only one iteration away. [*][b]A brief sprint retrospective, at which all team members reflect about the past sprint.[/b] Feeding the lessons of the previous sprint into the next sprint allows the team to self-tune and achieve more with each increment. [/list] [color=#4D4D4D][font=Verdana, Arial, Helvetica, sans-serif][size=3]The Scrum process in a project can be visualized as a set of feedback loops with larger and larger cycle times. At the end of each two- to four-week “sprint” cycle, the project will have a working piece of software suitable for demonstration and discussion with the customer.[/size][/font][/color] [center][color=#4D4D4D][font=Verdana, Arial, Helvetica, sans-serif][size=3][url="http://www.refractions.net/expertise/agile/agile_diagram.jpg"][img]http://www.refractions.net/expertise/agile/agile_diagram_sm.jpg[/img][/url][/size][/font][/color][/center] [b] WHY AGILE?[/b] [color=#4D4D4D][font=Verdana, Arial, Helvetica, sans-serif][size=3] Because building software is not the same as building a bridge, and traditional engineering project management methodologies do not reflect the way software is built and the quality improvements that can be achieved by having customers involved in the process all the way through.[/size][/font][/color] [b] HOW IS AGILE DIFFERENT?[/b] [color=#4D4D4D][font=Verdana, Arial, Helvetica, sans-serif][size=3] As a customer, you will be engaged in the whole processy, not just at the requirements gathering stage. You will have full access to the project team, will receive regular demos of the project, and will have full access to the internal documentation and discussions that go along with software development. All to ensure that your participation is one of collaboration, not negotiation.[/size][/font][/color] [b] HOW IS AGILE THE SAME?[/b] [color=#4D4D4D][font=Verdana, Arial, Helvetica, sans-serif][size=3] Planning and requirements are still carried out in an agile process, the increments of planning and delivery are just smaller. Instead of delivering the whole project in one development increment, several increments are used, with opportunities for review and change at each successive planning stage[/size][/font][/color]
karna11 Posted June 10, 2013 Author Report Posted June 10, 2013 [quote name='ICANWIN' timestamp='1370825929' post='1303840260'] [b] What is Agile?[/b] [color=#686868][font=Arial, Helvetica, sans-serif][size=3]Agile methodology follows an iterative approach in the development of the software. This helps to minimize the overall risk, and allows the project to adapt to changes quickly and does not require a requirements freeze upfront. Work is carried out in iterations, which typically last one to six weeks.[/size][/font][/color] [color=#686868][font=Arial, Helvetica, sans-serif][size=3][img]http://www.innolance.com/sites/all/themes/framework/images/delivery_agile.gif[/img] Agile development methods emphasize effective communication over written documents. The Project requirements are well documented upfront. Then, depending upon business priority, these features are assigned to releases, which are tied to iterations. Each agile team will contain a customer representative.[/size][/font][/color] [color=#686868][font=Arial, Helvetica, sans-serif][size=3]Agile development methods emphasize working software as the primary measure of progress. There are several popular agile methodologies like Scrum and Extreme Programming (XP). One of the fundamental ideas of XP is that not one process fits every project, but rather, practices should be tailored to the needs of individual projects. Almost all agile methods are suitable for method tailoring. We create a customized process for each client, taking his specific needs into account. We understand the importance of customization when it comes to client requirements.[/size][/font][/color] [url="http://www.innolance.com/process#agile"][Back to top][/url] [b] Why Agile?[/b] [color=#686868][font=Arial, Helvetica, sans-serif][size=3]As of 2009, the waterfall model is still in common use. Progress is generally measured in terms of deliverable artifacts: requirement specifications, design documents, test plans, code reviews and the like.[/size][/font][/color] [color=#686868][font=Arial, Helvetica, sans-serif][size=3]The main problem with the waterfall model is the inflexible division of a project into separate stages, so that commitments are made early on, and it is difficult to adapt to changes in requirements. This means that the waterfall model is likely to be unsuitable if requirements are not well understood or are likely to change in the course of the project. The waterfall model is bureaucratic, slow, demeaning, and inconsistent with the ways that software developers actually perform effective work.[/size][/font][/color] [color=#686868][font=Arial, Helvetica, sans-serif][size=3]Agile development methods produce completely developed and tested features of a small subset of the project once in every few weeks. The emphasis in Agile methodology is on obtaining the smallest workable piece of functionality to deliver business value early, and continually improving it and adding further functionality throughout the life of the project.[/size][/font][/color] [url="http://www.innolance.com/process#agile"][Back to top][/url] [b] Why other methodologies fail:[/b][list] [*]Lack of end-user (customer) involvement [*]Poor requirements [*]Unrealistic schedules [*]Lack of change management [*]Lack of testing [*]Inflexible and bloated processes [/list] [url="http://www.innolance.com/process#agile"][Back to top][/url] [b] Why is Agile successful?[/b] [list] [*]The web-based model allows companies to launch a bare bones version of the product first, get feedback from end-users and then incrementally add new features based on that feedback. [*]Products have to be developed with the latest technologies in a short time frame incorporating the need to changes so that the product is not outdated by the time of launch. [*]Agile may not address every software development problem, but it is a very profound step in the right direction. [/list] [color=#686868][font=Arial, Helvetica, sans-serif][size=3]It makes a serious attempt at addressing many of the key problems with current software development processes by empowering and respecting the people who are part of the process and by taking a pragmatic and realistic approach to the software development business. In this respect, agile critics may assert that these features are not placed in context of the overall project, concluding that, if the sponsors of the project are concerned about completing certain goals with a defined timeline or budget, agile may not be appropriate. Proponents of agile development counter that, adaptations of Scrum show how agile methods are augmented to produce and continuously improve a strategic plan.[/size][/font][/color] [url="http://www.innolance.com/process#agile"][Back to top][/url] [b] What is SCRUM?[/b] [color=#686868][font=Arial, Helvetica, sans-serif][size=3]Scrum is an iterative incremental process of software development commonly used with agile software development. It is the default process we use. Scrum can be implemented at the beginning of a project or in the middle of a project or product development effort that is in trouble -often within thirty days.[/size][/font][/color] [color=#686868][font=Arial, Helvetica, sans-serif][size=3]Scrum is a set of interrelated practices and rules that optimize the development environment, reduce organizational overhead, and closely synchronize market requirements with iterative prototypes. Based on modern process control theory, Scrum causes the best possible software to be constructed given the available resources, acceptable quality, and required release dates. Useful product functionality is delivered every thirty days as requirements, architecture, and design.[/size][/font][/color] [color=#686868][font=Arial, Helvetica, sans-serif][size=3]A key principle of Scrum is its recognition that during a project the customers can change their minds about what they want. Scrum accepts the fact that no problem can be fully understood or defined and hence focuses on maximizing the team's ability to deliver quickly and respond to emerging requirements. One of Scrum's biggest advantages is that it is very easy to learn and requires little effort to start using.[/size][/font][/color] [/quote] thanx dude,
karna11 Posted June 10, 2013 Author Report Posted June 10, 2013 [quote name='innovative' timestamp='1370825988' post='1303840265'] particular ga em pdf cheppu ... [/quote] aa thread link anukuntaaa
Recommended Posts