• Software Development Methodologies

    As these days I am writing about Scrum which is one of the agile methodologies, I though it could be nice if I can also list the other popular software development methodologies. Image via Wikipedia I have listed all these and also linked them to wiki as it has one of the very good definitions and details about every agile methodology. Once I am done with the Scrum series I will touch the other ones. Hope this helps! Agile Cleanroom Iterative RAD RUP Spiral Waterfall Lean V-Model TDD

  • Messages: WebSphere Application Server, Version 5.1.x

    Here are some of the common messages that you may get while working with Websphere Application Server 5.1.x. I found this list at IBM publib: WSVR0001I: Server {0} open for e-business Explanation: This exception is unexpected. The cause is not immediately known. User Response: If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. WSVR0002I: Server {0} open for e-business, problems occurred during startup Explanation: This exception is unexpected. The cause is not immediately known. User Response: If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. WSVR0003E: Server {0} failed to start {1} Explanation: This…

  • SCRUM: Artifacts

    Product Backlog The product backlog is a document that contains the list of all desired work on the project. All these entries have an overall description, priority based on business value and rough estimates specified. This document is owned by the Product Owner and he/she sets the business value for each item. While the team is responsible for updating the development estimates in the document. This document is re-prioritized at the start of each and every sprint. Sprint Backlog Sprint Backlog is a team document that is used to plan how the features will be implemented. In this document the team breaks the features into tasks. Normally these tasks are…

  • SCRUM: All the different Meetings

    Image by alandd via Flickr Sprint Planning Meeting Planning must be done at the beginning of every sprint cycle. Team selects items from the product backlog they can commit to completing Sprint backlog is created by the entire team. Tasks are identified and each is estimated (1-16 hours) Collaboratively, not done alone by the ScrumMaster An Eight hour limit applies to this meeting. During the 1st 4 hrs The Product owner and team prioritizes the product backlog and later only team plans the sprint and creates the Sprint Backlog. Time limit: 8 hrs Daily Scrum (Daily Standup) Meeting Daily Scrum is more like a daily project status meeting which is…