WordPress database error: [Can't create/write to file '/tmp/#sql-temptable-1-379-3.MAI' (Errcode: 28 "No space left on device")]SHOW FULL COLUMNS FROM `wp_options`
Personal projects can quickly become lost by the wayside. The initial momentum is difficult to maintain throughout the project cycle. That\u2019s why it\u2019s always good to consider how you\u2019re going to manage the project early on. Part of this process should be to consider how you intend to keep the project active in your consciousness and how to keep delivering features.<\/p>\n
Approach<\/strong><\/p>\n From the outset, we knew we were going to run the project with an Agile methodology. So delivering key features from the project backlog quickly as part of a 2-week sprint cycle was how we intended to deliver the application.<\/p>\n Tools<\/strong><\/p>\n In an ideal world where money isn\u2019t a concern, I would always recommend going down the Atlassian route. Their products are second to none with seamless integration between them making the process completely pain-free. However, it is expensive. The current MFE budget erm is \u00a30. Fundamentally, all you need is a well-organised spreadsheet that can be shared. Google docs to the rescue. We have 3 spreadsheets.<\/p>\n The first 2 sheets are fairly similar and contain a list of features and bugs with priorities against each. Each item has a unique number against it so it can be tracked.<\/p>\n The sprints spreadsheet has a tab for each sprint. The sprint will contain a list of features\/bugs for that 2-week sprint. There is also a tab to log how many story points were achieved in each sprint. Setting out 2 weeks’ worth of work is a good way of ensuring the project is moving forward. A sprint is a commitment of work that WILL<\/strong> be completed.<\/p>\n\n
<\/a><\/p>\n