Agile development with developer view !

[texsum]

this article intends to share the experience of running projects using development software interfaces in the organization of Agile. And to have the opportunity to join the team used this method to see the different perspectives. From reading or hearing from others I think that would be useful for readers to be studied and applied. Or supplement the existing development process.

The important thing to remember is always Agile methods no fixed rules that must be one, two, three steps Agile principle itself is a loose focus on people And communicate effectively in a team to process sub process is not waiting any steps that create difficulties. Or not suitable for corporate environments. I need to adjust accordingly. Currently there are several ways the Bureau of Development Agile were classified as XP, Scrum, Agile Modeling, Lean, etc are used which would have to depend on the readiness of the organization. Organization like a fictional example, I will tell you the following.

Large companies that employ thousands IT teams who are a hundred. The distribution of different floor of the building. IT team to develop this software's own enterprise. Using Java technology. Connected to mainframe systems. To employees and customers to use an applications via the Web from anywhere. Current systems are developing new versions. The main features added are not doing that. And must be used in conjunction with the current system is complex. And must be done within a limited time a few months. B look that process and the current team can not develop Software's time to finish in time to set certain I want him to hire consultants to help develop and manage projects.

This is not an organization that used an Agile development methods before, so people in the IT department and IT executives themselves do not ensure that this method will apply. No person or organization. What we do is to test this process with a small pilot project. See results from both software and software developed and the opinions of anyone associated. Elbow with this project. Results show that the results come out good impression people involved. The Map. Riches confidence. And how to go forward with full development of this method. And the consulting firm is responsible for project management prepare and coordinate with all parties.

Important management of large projects. Is planning Resource Management. What kind of planning, but not too much Why so upset over time. And not least to know that until the team is responsible for which part. Companies themselves rich. A rough division of labor in the form of Use Case in the tens unit. But each is large and complex It covers the full range of business processes. However, it is considered a good starting point. This time we will share the work with a team of consultants and contractor employees who do hundreds of major. I would ask troops to story details in the next For now I would like to summarize the steps that outline the best practices for the topics described in the subsequent following.

Joint Devepment level.
1. Plans and project management. Speaking to the division of labor. Resource use Including division team. And planning time.
2. The Weekly sprint update given less than forty-five minutes every week. Meeting for anyone listening to the progress of each team and / or talk about any problems with the team. Spare the other team can help with that.
3. Gantt chart for planning and monitoring the progress of each team to Burn up chart and table plan, each team will plan each week and work in the past week.
4. Administration projects that by eliminating unnecessary steps as possible. Including a bold decision to cut off non-critical features or less important than Move into the next version.

Team level.
1. The roles within the team. The Project Manager. Coordinator within the team. And between teams. Analyst contact with users and client representation. Developers who develop software's. And testers to control the quality of the work to the level desired. The person may assume the role of more than one time. Depending on the size of the team. Within each role with more than one person. It will be the leader. The people decide and coordinate with the leader of another team.
2. Release Planning meeting that month or less. Plan scheduled release.
3. Iteration Planning Meeting Weekly meeting to plan Sunday will be a user story and how some votes that each subject would take much.
4. Meetings Stand up meeting every morning to stand at every meeting. To force no longer talk to each one. Each person will report progress on what they do ago. Problems at bay. And things to do today
5. For the development team.
5.1 Support systems such as source version control, continuous integration tool, IDE, unit test, software metrics / analysis, bug tracking, instant messaging.
5.2, developed by the user story card, pair programming, refactoring, test driven development, and each user story must be tested and certified by the user or user agent.
5.3 Use the wall to benefit. The updated project status. Anyone can tell the back page of the project by walking to read
6. Meeting retrospective. Every Sunday to listen to opinions of everyone on the team each Sunday to see the advantages. Items that should improve. And suggest what can be implemented.
http://software-document.blogsp ot.com/2010/07/agile-development-in-developers-view.html