As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 10 years ago.
I am new to AGILE development but i have a strong background in java and php. I need to do a CRUD application (university application and registration web app) as fast as possible and want recommendations on the best, fastest and easiest to learn AGILE dev framework for my work with preferably MySQL for data store.
Agile has nothing to do with which technologies you use to implement your application. It's about the methodology you use to build your app. The two are orthogonal.
I'd recommend Spring if you want a good framework for developing a web app in Java. But Spring won't care if you use agile, waterfall, or anything other methodology.
What do you mean by agile development framework?
By wikipedia:
"Agile software development is a group of software development methodologies based on iterative and incremental development, where requirements and solutions evolve through collaboration between self-organizing, cross-functional teams"
So agile is a way how you manage your project, not a framework in which you work (you can develop in agile way in any language).
Of course by agile you can understand sets of software development practices as:
Unit testing
TDD
Solid principles
which you can easier implemented using additional frameworks/tools
I'm not sure if methodology choices are necessarily "orthogonal" to technology choices (as stated above). For example, most contemporary implementations of Agile strongly recommend practices such as TDD, unit testing, continuous integration, QA automation and the like. These practices are easier to adhere to if you make the right technology choices. The technology stack I've had most success with is as follows: Spring, Hibernate, Maven, Eclipse, Hudson, Log4J, JBoss, JUnit, soapUI. However, the above list is merely a guideline and is not comprehensive. One could, for example, easily swap Hudson for CruiseControl and perhaps be equally successful.
Related
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 5 years ago.
Improve this question
We are a small development team of 3. We are responsible for the design, development, test, and publish of each software application. We also provide software support, and deal with any issues the users may have, as well as bug fixing.
At the moment, each developer is solely responsible for seeing a project through from start to finish. So they will discuss with the client the requirements for the software. They will plan, design, and develop the software (both front-end and back-end). And they are responsible for testing and bug fixing.
Is this a development process that is recommended or should each developer be designated a number of tasks on each project?
I have been thinking of applying SCRUM principles to our development process but not sure how effective they would be. From what we do I gether that we are already working in an agile methodology with short iterations, and requirement discussions with the client?
Would you recommend SCRUM for our environment? How do other small teams operate?
It depends what is your purpose: implementing Agile just because it is the newest 'fashion' might prove to be very costly for your existing business.
In my experience (almost 15 years, now) it is better to implement Agile all around the company, not only at Tech level (or DevOps as they are now calling it).
If you implement any Agile method in a development environment than you simply get a bit more efficiency in that environment, only! A coder can not write more than that number of lines a day. Than, because the rest of the business is still at 'waterfall' your development side becomes a bottleneck by having to lag because of the rest...
In your particular case, perhaps it would be a good idea to get together with the developers and ask them: Agile or status quo? Once ALL of you agree for Agile than just go for it - first do it by the book and after a few sprints just start adapting what you need to your given situation. Perhaps a bit of pair-programming, a bit of cross-collaboration etc At the end of the day you are only three people: how difficult can it be to obtain consensus? funny
As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 9 years ago.
I am new to Node.js. I am very keen about learning it from scratch. I have a project which is like a Social media advertising web app. It won't be like Facebook, it is more like Myspace. It will be small at first, but it may become big in the future.
I would like to know if it's better to:
Use Node.js without a ready-made framework
Using an existing framework like Express, Geddy
I have done some research on sites out there using Node.js, and there are good sites that use a ready-made framework, and there are sites that don't. Is it worth creating our own site from scratch, or is it better to use a framework? Will using a framework restrict my ability to design my app and get in the way of learning Node.js?
So I would like to know that should I choose a framework or not. I am fine with learning Node.js from scratch and I'm not in a hurry or something.
The followup question is that there are lots of coding tutorials out there, but I would like some resources on the non-coding parts, such as software design, structure, etc..
Thanks for answering in advance.
Express, don't give it a second thought as a beginner.
While you may be interested in learning "from scratch" - you mention you are trying to develop a project which I assume should takes precedence over developing a framework.
Express, and node in general, is not that high-a-level of abstraction so you are not "losing" power as you may with a Java, etc framework.
You haven't mentioned anything hard or exotic that warrants a DIY framework. Even if you need that at some point, you will gain experience in node/express way of doing things first.
As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 10 years ago.
Im looking for a great agile scrum tool that allows me to do histories, epics, and tasks, file uploads to histories or tasks, and integrate those with github commits, also it should allow to create graphics like time analytics per user and activities and project results graphs and stuff like that...
Im hoping to use something cloud related, if its free better... yet Im willing to pay if its worth it!
What Im looking for is to introduce the agile methodology into a 4 month project that I have with 4 friends, were looking to build our own company.
Thank you for your help!
=== EDIT ===
Ive been looking at the tools you guys have provided, still have not decided, and I found another one all may find useful, but as i said i have not decided, so have you guys checked TargetProcess.com seems interesting?
You can check out https://sprint.ly/ and http://www.pivotaltracker.com/
JetBrain's YouTrack might be a good fit for you since it's free for up to 9 users and its Agile Project Management piece is also free for the first year and has integration with GitHub.
One of the nice project management tools I have experience with is Trac. It's 100% and really easy to use. The UI is pretty simple but it is very useful. Ass addition of that it comes with Subversion integrated. Probably now you think that that will be very painful for configuration. Actually there is a bundle http://bitnami.org/stack/trac where you can find all that environment set it up and ready to use.
Check out JIRA
I think it will fit your needs and offers various reports.
As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 9 years ago.
Are there any good multi-tenant Azure sample applications? Ideally I'd like to see some level of
Customization of data model
Customization of business logic
Customization of user interface
Automated tenant provisioning
Ideally front-end based on ASP.Net MVC3 and HTML5.
I found an old MS sample (Riviera) but it was from 2009. Also found Cloud Ninja (seems quite focused on metering), and Fabrikam Shipping Sample.
Any others I have missed? Also any other good resources/blogs on the subject?
To start, take a look at Cloud Ninja, both with a .NET implementation and a Java implementation. You'll find several interesting areas, including:
provisioning
identity management
multi-tenant database management
tenant-level metering
I saw that you mentioned Cloud Ninja, but I wanted to clarify it's not just about metering. Tenant provisioning is key, and this is demonstrated in both .net and java versions.
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 5 years ago.
Improve this question
A few years ago I have worked on a green field project where we did Extreme Programming. I also see a lot of people mention the Scrum methodology.
Could someone tell me the main differences between Scrum and XP?
Scrum is a software development methodology, XP is a programming practice. Both are "agile" techniques and are often used together.
Scrum outlines a process for identifying and cataloging work that needs to be done, prioritizing that work by communicating with the customer or customer representative, and implementing that work using iterative releases.
When my team first started experimenting with Scrum I found the Implementing Scrum website to be helpful.
Scrum is lightweight framework for building a product where there is high levels of complexity and uncertainty. It is NOT a methodology, as methodologies and practices can be chosen and used in conjunction to Scrum. It is not purely aimed at software development and can be used by other types of projects too.
When it comes to software engineering, Scrum does not define what practices to follow or methods follow as it does not want to prescribe what is best for that particular product and environment.
Many Scrum teams use several XP practices such as Testing, Feedback, Pair Programming and Simplicity.
The core differences
Scrum plans for a sprint and does not encourage change. XP is more open to change.
XP solicits feedback immediately and Scrum at least at the Sprint Review, however Scrum does not reject early feedback if possible.
XP focuses on programming, Scrum can be used in non software products
Scrum does not define how to do development, but many Scrum teams implement many of the XP practices
I've worked on both. Some of the main differences are that SCRUM focuses on the shorter more structured sprints, and prioritizes back log items. Some of the focuses of XP are more on paired programming, prioritizing the tasks, and more test driven development. Both work in iterations and both are flexible enough to handle a volatile changing project.
Scrum is one component of the Agile development methodology concerning the daily meeting held to discuss progress and XP is a different methodology stressing pair programming and test first development.
Scrum's main goal is to get estimations of how long development will take. XP is more about helping developers get things done as quickly and maintainably as possible.