The majority of my experience has involved the generation of software development life cycles–how they are managed, by whom, and for what purpose. I used this experience to create a template from which I could include the best practices encouraged from the numerous best-of-breed development methods at my disposal; my main sources of references being Extreme Programming(XP), Scrum, iterative development, and agile development.
From these methods, I focused on developing a life cycle that could encompass the following best-of-breed practices from these best-of-breed agile methods:
The keystone for my life cycle was user stories:the ability to articulate requirements in sufficient detail to allow a reasonable development estimate to be made. In terms of managing user stories with technology, Harvest packages and their related electronic forms were designed to capture the necessary information for a standard user story.
Life-cycle workflow 1
Once the user stories were created, it was necessary to under go formal validation and iteration planning(development planning) – the process of assigning user stories to particular iterations, or sprints, based on resources, effort and priority. Modeled in Harvest,1 this process looked as shown in Figure.
You will notice that the terms are not literally extracted from the methods in which they originally belong;this was to reduce the “cultural shock” and make the transition more seamless for the end users.
From iteration planning(development planning) the user story could be sent to the development team, either as a planned piece of work or as a support and maintenance development.
Depending on the customer requirements, support and maintenance could also take on the role of “spike development,” as per the XP method. For this particular customer, the principle of working on the latest version of the code, in an isolated environment on the branch, lent itself to support and maintenance development but could have easily been labeled “spike development” with no functional changes to the SCM product.
The resulting life cycle process was further developed as shown in Figure. It is in development that the continuous integration builds were implemented;this will be covered in more detail later in this section.
Assuming a successful build was produced, the user stories would then be promoted through the SCM product to a staging area where the business acceptance could take place. Once the business had accepted the changes, they would be promoted for a minor release.
In the event that the business required rework, the user story was demoted back to development where the necessary changes could be made and the user story reused
to repeat the process. The advantage of using a tool for managing the process means that workflow information can be continually tracked–identifying the proportion of “new development” versus “rework,” for example, may be an extremely useful metric of the productivity of the team, how accurate the requirements are being specified, or the capability of the assigned developers see Figure. This completes the end-to end application life cycle, as shown in Figure.
Life-cycle workflow .
Life-cycle workflow .
From Figure the process should become clear with respect to what has been implemented and how it has been influenced by various development methods.
Agile Testing Related Interview Questions
|ETL Testing Interview Questions||Manual Testing Interview Questions|
|Selenium Interview Questions||Database Testing Interview Questions|
|Automation Testing Interview Questions||Software testing Interview Questions|
|Performance Testing Interview Questions||Embedded Testing Interview Questions|
|A/B Testing Interview Questions||Hadoop Testing Interview Questions|
Agile Testing Tutorial
Old-school Development And Testing
Agile Development And Testing
From Waterfall To Evolutionary Development And Test
How To Test A System That Is Never Finished
Implementing An Agile Testing Approach
Agile Testing In A Remote Or Virtual Desktop Environment
Testing A Derivatives Trading System In An Uncooperative Environment
A Mixed Approach To System Development And Testing: Parallel Agile And Waterfall Approach Streams Within A Single Project
Agile Migration And Testing Of A Large-scale Financial System
Agile Testing With Mock Objects: A Cast-based Approach
Agile Testing – Learning From Your Own Mistakes
Agile: The Emperor’s New Test Plan?
The Power Of Continuous Integration Builds And Agile Deve- Lopment
The Payoffs And Perils Of Offshored Agile Projects
The Basic Rules Of Quality And Management Still Apply To Agile
Test-infecting A Development Team
Agile Success Through Test Automation: An Extreme Approach
Talking, Saying, And Listening: Communication In Agile Teams
Very-small-scale Agile Development And Testing Of A Wiki
Agile Special Tactics: Soa Projects
The Agile Test-driven Methodology Experiment
When Is A Scrum Not A Scrum?
Analysis Of The Case Studies
My Agile Process
The Roll-out And Adoption Of My Agile Process
All rights reserved © 2018 Wisdom IT Services India Pvt. Ltd
Wisdomjobs.com is one of the best job search sites in India.